Bug#776696: please update GTK+3 in Jessie to the latest 3.14.x bugfix release

[Mert Dirik]

Wow you're fast! Thank you very much for your effort. I hope it gets
an ACK soon.

On Tue, Aug 18, 2015 at 12:13 AM, Ruben Undheim <ruben.undheim at gmail.com> wrote:
> Then I've filed a request:
>   https://bugs.debian.org/795911
>
> Let's see how it goes. :)
>
> Ruben
>
> 2015-08-17 22:44 GMT+02:00 Mert Dirik <mertdirik at gmail.com>:
>> On Mon, Aug 17, 2015 at 11:37 PM, Ruben Undheim <ruben.undheim at gmail.com> wrote:
>>> Hi,
>>>
>>> Thanks Mert.
>>>
>>> Then, we've tested all of them.
>>>
>>> My test results:
>>>
>>> #787419: OK
>>> reproduced the same way you did
>>> fixed with patched version
>>>
>>> #748469: OK
>>> reproduced multiple times by opening font chooser in gnome-terminal -
>>> selecting one font - and searching for another
>>> fixed with patched version
>>>
>>> #773135: OK
>>> I did what you described here. First installed emacs, then chose "Open
>>> with" in nautilus.
>>> Big icon with original version. Normal icon size with patched version
>>>
>>> #771205: Fail
>>> Not able to reproduce - nor see the fixed result
>>>
>>> #788002: OK
>>> I downloaded the MP3 file that was linked to in the original bug
>>> report. I removed the newlines from the comment field with easytag on
>>> a system with a newer version of gtk, and then opened it with Jessie's
>>> gtk. easytag crashed
>>> After installing patched version - problem gone.
>>>
>>>
>>> I agree with you, I remove #771205 for now. I will file a
>>> release.debian.org bug report and see what response we get.
>>>
>>> It would however be nice if someone from the pkg-gnome team could give
>>> us some feedback. Based on the response from Andreas H. [1], I assume
>>> that it is ok that we contact the Stable release team. It seems like
>>> we care more about these things being fixed in Jessie than the
>>> maintainer team, so it is probably fair that we do that job.
>>>
>>>
>>> [1] http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/2015-August/121106.html
>>>
>>
>> Okay, that's great.
>> I think it should be OK as long as we explain why *we* open the bug
>> report and provide a link to the Andreas' mail. After getting and ACK
>> we should ask for either sponsorship or a new upload by the
>> maintainers themselves.