Your message dated Sat, 1 Jul 2017 16:59:24 -0500
with message-id <[email protected]>
and subject line Re: Bug#864321: libgtk-3-0: New upstream release 3.22.15 
available
has caused the Debian Bug report #864321,
regarding libgtk-3-0: New upstream release 3.22.15 available
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
864321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864321
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libgtk-3-0
Version: 3.22.12-1
Severity: normal
Tags: upstream

Dear Maintainer,

There is a new upstream version available, 3.22.15.

http://ftp.gnome.org/pub/gnome/sources/gtk+/3.22/gtk+-3.22.15.tar.xz

For a look at changes since 3.22.12:

https://fossies.org/linux/gtk+/NEWS


-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.3-josep1 (SMP w/4 CPU cores)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), LANGUAGE=ca 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libgtk-3-0 depends on:
ii  adwaita-icon-theme                      3.22.0-1
ii  hicolor-icon-theme                      0.15-1
ii  libatk-bridge2.0-0                      2.22.0-2
ii  libatk1.0-0                             2.22.0-1
ii  libc6                                   2.24-11
ii  libcairo-gobject2                       1.14.8-1
ii  libcairo2                               1.14.8-1
ii  libcolord2                              1.3.3-2
ii  libcups2                                2.2.1-8
ii  libepoxy0                               1.3.1-2
ii  libfontconfig1                          2.11.0-6.7+b1
ii  libfreetype6                            2.6.3-3.2
ii  libgdk-pixbuf2.0-0                      2.36.5-2
ii  libglib2.0-0                            2.50.3-2
ii  libgtk-3-common                         3.22.12-1
ii  libjson-glib-1.0-0                      1.2.6-1
ii  libpango-1.0-0                          1.40.5-1
ii  libpangocairo-1.0-0                     1.40.5-1
ii  libpangoft2-1.0-0                       1.40.5-1
ii  librest-0.7-0                           0.8.0-2
ii  libsoup2.4-1                            2.56.0-2
ii  libwayland-client0                      1.12.0-1
ii  libwayland-cursor0                      1.12.0-1
ii  libwayland-egl1-mesa [libwayland-egl1]  17.1.0-1
ii  libx11-6                                2:1.6.4-3
ii  libxcomposite1                          1:0.4.4-2
ii  libxcursor1                             1:1.1.14-1+b4
ii  libxdamage1                             1:1.1.4-2+b3
ii  libxext6                                2:1.3.3-1+b2
ii  libxfixes3                              1:5.0.3-1
ii  libxi6                                  2:1.7.9-1
ii  libxinerama1                            2:1.1.3-1+b3
ii  libxkbcommon0                           0.7.1-1
ii  libxml2                                 2.9.4+dfsg1-2.2
ii  libxrandr2                              2:1.5.1-1
ii  shared-mime-info                        1.8-1

Versions of packages libgtk-3-0 recommends:
ii  libgtk-3-bin  3.22.12-1

Versions of packages libgtk-3-0 suggests:
ii  gvfs             1.30.4-1
ii  librsvg2-common  2.40.16-1+b1

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 3.22.16-1

On Sat, Jul 01, 2017 at 01:41:29AM +0200, Josep Febrer wrote:
> This bug has already been fixed by the recent upload of Gtk 3 3.22.16-1 and 
> can 
> be closed.

--- End Message ---

Reply via email to