commit d4b60396c79c7294ab69a2c591518e76ab17b603
Author: Matthias Clasen <mclasen@redhat.com>
Date:   Thu Aug 16 20:24:55 2018 -0400

    2.56.2

 NEWS         | 28 ++++++++++++++++++++++++++++
 configure.ac |  4 ++--
 meson.build  |  2 +-
 3 files changed, 31 insertions(+), 3 deletions(-)

commit d0f6a59fb0e039b1040c64bb14d7ad6bfc6c5ad5
Author: Matthias Clasen <mclasen@redhat.com>
Date:   Thu Aug 16 21:36:13 2018 +0000

    network monitor portal: update properties initially

    With version 2, we need to query the values explicitly.
    The properties made this automatic.

 gio/gnetworkmonitorportal.c | 21 +++++++++++++++++----
 1 file changed, 17 insertions(+), 4 deletions(-)

commit 7ddd1de0ddc066ffec584cab26792be395d8e8d4
Author: Matthias Clasen <mclasen@redhat.com>
Date:   Fri Jul 20 18:53:57 2018 -0400

    network monitor: Update portal implementation

    The network monitor portal interface is changing.
    Version 2 is no longer using properties, but getters
    instead (this lets the portal apply access control
    and avoid sending information to non-networked
    sandboxes).

    To support both version 1 and 2 of the interface,
    we stop using generated code and instead deal with
    the api differences in our own code, which is not
    too difficult.

    Support version 1 as well

 gio/gnetworkmonitorportal.c                   | 236
 ++++++++++++++++++++++----
 gio/org.freedesktop.portal.NetworkMonitor.xml |  81 +++++++--
 2 files changed, 278 insertions(+), 39 deletions(-)

commit edcce31f8ecabf37fc13bf62fb59212fa1a86081
Author: Milan Crha <mcrha@redhat.com>
Date:   Tue Apr 10 15:27:00 2018 +0000

    gnetworkmonitor: Fix use-after-free when using from another thread

    When using g_network_monitor_get_default() from another thread, it’s
    possible for network-changed events to be processed after an
    instance of
    GNetworkMonitor has been disposed, causing use-after-free problems.

    Fix that by moving some of the initialisation into the
    GInitable.init()
    chain, rather than in a main context idle callback.

    This includes a unit test which probabilistically reproduces the bug
    (but can’t do so deterministically due to it being a race
    condition).

    Commit amended by Philip Withnall <withnall@endlessm.com> before
    pushing.

    https://bugzilla.gnome.org/show_bug.cgi?id=793727

 gio/gnetworkmonitorbase.c        | 30 +++++++------
 gio/gnetworkmonitornetlink.c     |  5 ++-
 gio/gnetworkmonitorportal.c      |  6 ++-
 gio/gwin32networkmonitor.c       |  5 ++-
 gio/tests/Makefile.am            |  1 +
 gio/tests/meson.build            |  1 +
 gio/tests/network-monitor-race.c | 92
 ++++++++++++++++++++++++++++++++++++++++
 7 files changed, 122 insertions(+), 18 deletions(-)

commit 0b4e82176327493ee93f125fca781d396ae3a00c
Merge: d338fdaf7 2c1aee196
Author: Ondrej Holy <oholy@redhat.com>
Date:   Thu Aug 9 14:50:51 2018 +0000

    Merge branch 'cherry-pick-volume-mount-2-56' into 'glib-2-56'

    Cherry pick GVolumeMonitor mount changes to glib-2-56 from issue #1458

    See merge request GNOME/glib!224

commit d338fdaf754a11d1e7cd0d9b2cdddc648da42157
Merge: 86b5b440a 7fa2ad51a
Author: Philip Withnall <philip@tecnocode.co.uk>
Date:   Thu Aug 9 10:12:46 2018 +0000

    Merge branch '1452-backport-glib-2-56' into 'glib-2-56'

    Backport GFileInfo win32 fixes to glib-2-56

    See merge request GNOME/glib!237

commit 7fa2ad51a8233add4ad6363edb3c95cba96e6147
Author: Руслан Ижбулатов <lrn1986@gmail.com>
Date:   Wed Aug 8 21:42:45 2018 +0000

    W32: consider NTFS mounpoints to be symlinks

    While mountpoints are *not* symlinks, strictly speaking,
    they works in a similar enough way, so consider them to be
    symlinks for the purpose of querying local file info.

 gio/glocalfileinfo.c | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

commit 9f56652ceaa9285771b765bac7ff7fba648f9568
Author: Руслан Ижбулатов <lrn1986@gmail.com>
Date:   Wed Aug 8 21:39:43 2018 +0000

    W32: correctly use st_ctime

    On Windows st_ctime field is the file creation time.
    POSIX mandates that field to be the file state change time.
    Naturally, glib code interpreted st_ctime as POSIX suggested,
    and the result was bad.
    Fix this by introducing special W32-only logic for setting
    attributes from st_ctime field.

    Fixes issue #1452.

 gio/glocalfileinfo.c | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

commit 2c1aee1963700b65dc938519c0aaeee731e2aa8b
Author: Ondrej Holy <oholy@redhat.com>
Date:   Thu Aug 2 11:35:48 2018 +0200

    gio-tool: Hold GVolumeMonitor reference during operations

    Releasing GVolumeMonitor before g_volume_mount finish cause that
    g_volume_get_mount returns NULL, because the mount is not correctly
    propagated to the volume.

    (Backported from commit 88b8ebb5dde0512fd1e098efe4c217111876d252 with
    minor merge conflicts.)

    https://gitlab.gnome.org/GNOME/glib/issues/1458

 gio/gio-tool-mount.c | 23 ++++-------------------
 1 file changed, 4 insertions(+), 19 deletions(-)

commit f9ab355896993bb930c929bd0ddc3ace1b895cbe
Author: Ondrej Holy <oholy@redhat.com>
Date:   Mon Jul 30 15:26:31 2018 +0200

    gio: Update mounts after g_volume_mount

    The documentation claims that g_volume_get_mount should succeed after
    g_volume_mount. Let's update mounts before releasing g_volume_mount to
    be sure that the mount is added to the corresponding volume. The same
    is done in GVfsUDisks2VolumeMonitor.

    (Backported from commit 9b6b282e0a9d3f37865aa36e21ea57bd2a326e20
    with no
    merge conflicts.)

    https://gitlab.gnome.org/GNOME/glib/issues/1458

 gio/gunixvolume.c        |  9 +++++++--
 gio/gunixvolumemonitor.c | 19 +++++++++++--------
 gio/gunixvolumemonitor.h |  1 +
 3 files changed, 19 insertions(+), 10 deletions(-)

commit 86b5b440a8a7729dbff84d530f69a6b9e9293ceb
Author: Ondrej Holy <oholy@redhat.com>
Date:   Fri Jun 29 07:07:24 2018 +0000

    Merge branch 'cifs-is-not-a-system-fs' into 'master'

    gunixmounts: Stop considering cifs/nfs as system file systems

    See merge request GNOME/glib!125

    (cherry picked from commit 51132b1d49c184f49baafa81ce7fac02b1458643)

    a3a6c516 gunixmounts: Stop considering cifs/nfs as system file systems

 gio/gunixmounts.c       | 4 ----
 gio/tests/unix-mounts.c | 6 ++++++
 2 files changed, 6 insertions(+), 4 deletions(-)

commit baeaca4f316c2b2ef6b96cf3137e1df0e815e33b
Merge: 826676e82 d26b66e22
Author: Philip Withnall <philip@tecnocode.co.uk>
Date:   Wed Jun 13 14:28:15 2018 +0000

    Merge branch '1280-fdo-notification-glib-2-56' into 'glib-2-56'

    Backport "fdo notification backend: Crashes when dbus call fails"
    to glib-2-56

    See merge request GNOME/glib!102

commit d26b66e225d3f0d308b2ec1a862a505709076bf7
Author: Arnaud Rebillout <elboulangero@gmail.com>
Date:   Sun Jun 10 20:56:12 2018 +0700

    gfdonotificationbackend: Fix possible invalid pointer in dbus callback

    The way things were before: a FreedesktopNotification struct is
    allocated before the dbus call, and this same struct is possibly
    re-used
    for other dbus calls. If the server becomes unavailable, the callback
    will be invoked after the call times out, which leaves a long
    time where
    other dbus calls can happen, re-using the same FreedesktopNotification
    as user data. When the first call times out, the callback is invoked,
    and the user data is freed. Subsequent calls that used the same user
    data will time out later on, and try to free a pointer that was
    already
    freed, hence segfaults.

    This bug can be reproduced in Cinnamon 3.6.7, as mentioned in:
    <https://github.com/linuxmint/Cinnamon/issues/7491>

    This commit fixes that by always allocating a new
    FreedesktopNotification before invoking dbus_call(), ensuring that the
    callback always have a valid user data.

    Signed-off-by: Arnaud Rebillout <elboulangero@gmail.com>

 gio/gfdonotificationbackend.c | 55
 ++++++++++++++++++++++++++-----------------
 1 file changed, 34 insertions(+), 21 deletions(-)

commit 4a27a88d29eaf1e8835c815d0f63ee4da89599f0
Author: Philip Withnall <withnall@endlessm.com>
Date:   Wed Jun 13 14:07:18 2018 +0100

    ci: Use v3 of the Docker image for CI builds

    Don’t update to the full CI setup from master, since its success
    depends
    on other fixes which are only present in master. However, using v1 of
    the Docker image is no longer possible since it’s been removed
    from the
    registry. Using v3 should enable CI builds for glib-2-56 to succeed.

    Signed-off-by: Philip Withnall <withnall@endlessm.com>

 .gitlab-ci.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit 826676e826a50cca6de02c0f2f5c0d99d48b3e81
Merge: c0e6cc3a4 aaa00b5c9
Author: Philip Withnall <philip@tecnocode.co.uk>
Date:   Wed Jun 13 12:38:05 2018 +0000

    Merge branch '101-dbus-is-supported-glib-2-56' into 'glib-2-56'

    Backport "g_dbus_is_supported_address(): set error if returning FALSE"
    to glib-2-56

    See merge request GNOME/glib!103

commit aaa00b5c983b238de71e0dc45852070d7d294ea6
Author: Will Thompson <will@willthompson.co.uk>
Date:   Wed Jun 13 10:50:35 2018 +0100

    g_dbus_is_supported_address(): set error if returning FALSE

    Previously, calling:

        g_dbus_is_supported_address ("some-imaginary-transport:", NULL)

    correctly returned FALSE; but calling:

        g_dbus_is_supported_address ("some-imaginary-transport:", &error)

    crashed with:

        GLib-GIO:ERROR:../gio/gdbusaddress.c:434:g_dbus_is_supported_address:
        assertion failed: (ret || (!ret && (error == NULL || *error
        != NULL)))

    This was because, if the address component did not start with a known
    transport, no error was set. Fix this, reusing an error string used by
    the corresponding else branch in g_dbus_address_connect(), and adjust
    the test to pass both NULL and non-NULL GError **s to this function in
    every test case. This case:

        g_assert (!g_dbus_is_supported_address
        ("some-imaginary-transport:foo=bar;unix:path=/this/is/valid",
        NULL));

    would have caught this bug with a non-NULL GError **.

 gio/gdbusaddress.c          |  4 +++
 gio/tests/gdbus-addresses.c | 79
 ++++++++++++++++++++++++++++-----------------
 2 files changed, 54 insertions(+), 29 deletions(-)

commit c0e6cc3a4093acc73c15bca5a2b8e066477a0d8b
Merge: 69dec2db4 cfa28e152
Author: Xavier Claessens <xclaesse@gmail.com>
Date:   Tue Jun 5 14:43:36 2018 +0000

    Merge branch 'cherry-pick-95ebaa26' into 'glib-2-56'

    Merge branch '1401-g_clear_handle_id-clear_func-not-nullable' into
    'master'

    See merge request GNOME/glib!56

commit cfa28e152bef6614add71efea9a260036ee83652
Author: Philip Withnall <philip@tecnocode.co.uk>
Date:   Mon Jun 4 13:41:10 2018 +0000

    Merge branch '1401-g_clear_handle_id-clear_func-not-nullable' into
    'master'

    g_clear_handle_id: don't accept NULL clear_func

    Closes #1401

    See merge request GNOME/glib!55

    (cherry picked from commit 95ebaa26aa5b2a5f6e5ee554a6d185d296f6dc08)

    0f7c196c g_clear_handle_id: don't accept NULL clear_func

 glib/gmain.c | 3 +--
 glib/gmain.h | 3 +--
 2 files changed, 2 insertions(+), 4 deletions(-)

commit 69dec2db499fc97f36ee4f43e200ff8a5af06343
Merge: 0bc1e98af d5f1da8c3
Author: Philip Withnall <philip@tecnocode.co.uk>
Date:   Mon May 28 08:58:46 2018 +0000

    Merge branch 'lrn/issue-1240_glib-2-56' into 'glib-2-56'

    W32: Make _g_win32_get_system_data_dirs() inline available in C++
    (glib-2-56 backport)

    See merge request GNOME/glib!29

commit d5f1da8c398267a698b99251f9b7c2a3b857c14d
Author: Руслан Ижбулатов <lrn1986@gmail.com>
Date:   Thu Jan 19 18:53:34 2017 +0000

    W32: Make _g_win32_get_system_data_dirs() inline available in C++

    This way g_get_system_data_dirs() works the same way in C and C++.

    https://bugzilla.gnome.org/show_bug.cgi?id=777501

    Closes #1240

 glib/gutils.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit 0bc1e98af6f6ed2f4a5f05f495b0c9a001dc370f
Author: Руслан Ижбулатов <lrn1986@gmail.com>
Date:   Tue May 22 16:43:35 2018 +0000

    W32: check filename for being NULL in g_stat()

    Previous version of this function started with a call to
    g_utf8_to_utf16(),
    which also served as a NULL check, since g_utf8_to_utf16() just
    returns NULL
    on NULL strings. Current version of this function does some filename
    string
    checks first and converts it to utf16 only after these checks are
    done, and
    these checks do not take into account the possibility of filename
    being NULL.

    Fix this by explicitly checking for NULL.

 glib/gstdio.c | 6 ++++++
 1 file changed, 6 insertions(+)

commit 4c364635ede0048320a60a7267df802cdc7db693
Author: Nirbheek Chauhan <nirbheek@centricular.com>
Date:   Sat May 5 03:19:54 2018 +0530

    meson: Update glib version

 meson.build | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit 0489f609ca9f1c323801d5a2225590567d95a795
Author: Philip Withnall <withnall@endlessm.com>
Date:   Fri May 4 10:13:13 2018 +0100

    gobject: Reimplement g_param_values_cmp() for GParamSpecVariant

    The existing implementation was completely incorrect (despite the
    fix in
    commit 566e64a66) — it always compared GVariants by pointer,
    rather than
    by value.

    Reimplement it to compare them by value where possible, depending on
    their type. The core of this implementation is
    g_variant_compare(). See
    the documentation and tests for further details of the new sort order.

    This adds documentation and tests.

    Signed-off-by: Philip Withnall <withnall@endlessm.com>

    https://bugzilla.gnome.org/show_bug.cgi?id=795735

 gobject/gparamspecs.c          |  28 ++++++++++-
 gobject/gparamspecs.h          |   6 +++
 tests/gobject/paramspec-test.c | 104
 +++++++++++++++++++++++++++++++++++++++--
 3 files changed, 134 insertions(+), 4 deletions(-)

commit 69924c45b953ac0164ca0eafedba2cf9ae9b77dd
Author: Philip Withnall <withnall@endlessm.com>
Date:   Fri May 4 17:24:31 2018 +0100

    Revert "Fix the cmp implementation for variant values"

    This reverts commit 623f92ed2df41265c11c3ca1e03176033045d4de.

    This fix went from one broken state to another. The real fix is to use
    g_variant_compare(), which is pending review. See bug #795735.

    https://bugzilla.gnome.org/show_bug.cgi?id=795735

 gobject/gparamspecs.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit cd1f82d8fc741a2203582c12cc21b4dacf7e1872
Author: Iñigo Martínez <inigomartinez@gmail.com>
Date:   Fri May 4 16:23:18 2018 +0200

    gdbus-codegen: Fix header include in the body file

    When body file is generated, the header name to be included is
    built by using the path passed by `--output` directory. However,
    this might not be correct because, if the path includes a
    subdirectory, the whole path will be used instead of only the
    base name.

    Please see:
      https://github.com/mesonbuild/meson/issues/3488
      https://github.com/gnome-mpv/gnome-mpv/issues/305#issuecomment-385056156

    https://bugzilla.gnome.org/show_bug.cgi?id=795802

 gio/gdbus-2.0/codegen/codegen_main.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit 623f92ed2df41265c11c3ca1e03176033045d4de
Author: Matthias Clasen <mclasen@redhat.com>
Date:   Tue May 1 22:45:31 2018 -0400

    Fix the cmp implementation for variant values

    This was causing g_param_value_defaults to return 1
    for GVariant values even when the value is clearly
    different from the default.

    This was showing up as gtk-builder-tool stripping
    non-default values for GtkActionable::action-target
    from ui files.

 gobject/gparamspecs.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit 7132abe1e6985e4e9718bf1ada4f1d094b8e51f6
Author: Christoph Reiter <creiter@src.gnome.org>
Date:   Tue May 1 08:55:29 2018 +0200

    ci: update meson

    Rebuild the fedora docker image to get the newest meson release.

    (Backport 2.56: Tweaked by Philip Withnall <withnall@endlessm.com> to
    drop MSYS2 changes.)

    https://bugzilla.gnome.org/show_bug.cgi?id=795711

 .gitlab-ci.yml           | 2 +-
 .gitlab-ci/run-docker.sh | 6 ++++--
 2 files changed, 5 insertions(+), 3 deletions(-)

commit c96e45496c9097fba4e9be96b8487aa9eec8b7c9
Author: Philip Withnall <withnall@endlessm.com>
Date:   Thu Apr 26 11:14:48 2018 +0100

    gutils: Fix deadlock if g_get_home_dir() fails when called twice

    If g_get_home_dir() calculated a NULL home directory (due to $HOME
    being
    unset and /etc/passwd being inaccessible, for example due to an
    overly-zealous LSM), it would call g_once_init_leave (&home_dir,
    NULL),
    which would emit a critical and fail to leave the GOnce critical
    section. That meant that the following call to g_get_home_dir() would
    deadlock in g_once_init_enter().

    Fix that by setting the home directory to a made-up value in such
    cases
    (which the documentation handily already explicitly allows).

    Thanks to Simon McVittie for the analysis leading to an easy patch.

    Signed-off-by: Philip Withnall <withnall@endlessm.com>

    https://bugzilla.gnome.org/show_bug.cgi?id=773435

 glib/gutils.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

commit fea050d9d5a961c87366aa2290161f44a865cf77
Author: Philip Withnall <withnall@endlessm.com>
Date:   Fri Apr 13 17:02:23 2018 +0100

    tests: Drop a slightly suspect GResolver test

    This test will only work on machines which have IPv6 enabled and
    have a
    local IPv6 interface with ID 1. On machines which don’t (such as AWS
    servers, which we run CI tests on), the GResolver tests will fail with
    G_RESOLVER_ERROR_INVALID. We can’t differentiate this kind of
    failure
    (where we’d want to skip the test) from an actual failure (where
    we’d
    want to fail the test), so the only other option is to drop this
    particular test vector. I don’t think it’s a significant loss.

    This is the last fix needed to get our CI tests working reliably on
    jenkins.gnome.org.

    Signed-off-by: Philip Withnall <withnall@endlessm.com>

    https://bugzilla.gnome.org/show_bug.cgi?id=795234

 gio/tests/network-address.c | 5 -----
 1 file changed, 5 deletions(-)

commit 89463e0c53acf4656030e9ad8cf4ca5a06a55e78
Author: Philip Withnall <withnall@endlessm.com>
Date:   Fri Apr 13 16:11:43 2018 +0100

    tests: Skip GSocket tests if setting up a server fails

    There are various reasons why setting up a server might fail; it
    reliably fails on AWS with IPv6 addresses (are we binding to the right
    address?). Since we’re trying to test GSocket as a client,
    skip tests
    where that happens.

    Signed-off-by: Philip Withnall <withnall@endlessm.com>

    https://bugzilla.gnome.org/show_bug.cgi?id=795234

 gio/tests/socket.c | 129
 +++++++++++++++++++++++++++++++++++++++--------------
 1 file changed, 96 insertions(+), 33 deletions(-)

commit 51792786e63f8d57f8ece1fbc5e44087d3377ad2
Author: Xavier Claessens <xavier.claessens@collabora.com>
Date:   Mon Apr 23 10:33:44 2018 -0400

    Fix build when pthread_getname_np is not available

    On Android _setname_ is always available but _getname_ is available
    only
    with API level >= 26.

    https://bugzilla.gnome.org/show_bug.cgi?id=795406

 config.h.meson      |  3 +++
 configure.ac        |  9 +++++++++
 glib/tests/thread.c |  2 +-
 meson.build         | 18 ++++++++++--------
 4 files changed, 23 insertions(+), 9 deletions(-)

commit 297e9debe39a6a2ba6193da080dd50bd324e073b
Author: Xavier Claessens <xavier.claessens@collabora.com>
Date:   Fri Apr 20 12:09:32 2018 -0400

    Meson: Add missing link on libintl in tests

    This fix undefined symbol link error when building for non-glibc
    platform. Applications must link on libintl, it is not a public
    dependency of libglib.

    On glibc platforms libintl is a not found dependency and is just
    ignored
    by meson, so it doesn't hurt to always have it.

    https://bugzilla.gnome.org/show_bug.cgi?id=795406

 gio/tests/meson.build | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

commit 7ca9a04e828a27be75642a831fbf35443eb00b5d
Author: Xavier Claessens <xavier.claessens@collabora.com>
Date:   Mon Apr 23 11:47:17 2018 -0400

    struct ip_mreq_source definition is broken on Android NDK <= r16

    This fix the build on Android r16 and older, see:
    https://issuetracker.google.com/issues/36987220

    https://bugzilla.gnome.org/show_bug.cgi?id=740791

 config.h.meson  |  3 +++
 configure.ac    | 15 +++++++++++++++
 gio/gsocket.c   | 16 +++++++++++++---
 gio/meson.build | 10 ++++++++++
 4 files changed, 41 insertions(+), 3 deletions(-)

commit b757036b3fcec131aa3bb5bf07bfa0b2c0d6e31f
Author: Xavier Claessens <xavier.claessens@collabora.com>
Date:   Fri Apr 20 12:10:18 2018 -0400

    Tests: gsubprocess: Do not use stdin/stdout variables

    https://bugzilla.gnome.org/show_bug.cgi?id=795406

 gio/tests/gsubprocess.c | 54
 ++++++++++++++++++++++++-------------------------
 1 file changed, 27 insertions(+), 27 deletions(-)

commit 926a5c5e5389b6869e59f6c661f531e0b101c5fd
Author: Kentaro Hayashi <hayashi@clear-code.com>
Date:   Sat Apr 21 17:13:32 2018 +0900

    gobject: Fix redundant warning message in glib-genmarshal

    glib-genmarshal shows redundant "time" warning message against
    combination with --header and --body option.

    Before:

      WARNING: Using --header and --body at the same time time is
      deprecated; use --body --prototypes instead

    After:

      WARNING: Using --header and --body at the same time is deprecated;
      use --body --prototypes instead

    https://bugzilla.gnome.org/show_bug.cgi?id=795429
    Signed-off-by: Kentaro Hayashi <hayashi@clear-code.com>

 gobject/glib-genmarshal.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit 3975d54bca8db9bd23c28cab7493fbde0cf46111
Author: Stas Solovey <whats_up@tut.by>
Date:   Fri Apr 20 20:48:36 2018 +0000

    Update Russian translation

 po/ru.po | 109
 ++++++++++++++++++++++++++-------------------------------------
 1 file changed, 44 insertions(+), 65 deletions(-)

commit 8de72c56a02f1340f80ef3cc0fadff73823a471e
Author: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Date:   Tue Apr 10 19:18:57 2018 +0200

    gobject: fix compilation with gcc <= 4.7

    On gcc 4.7, we got the following error:

    i686-nptl-linux-gnu-gcc --version
    > i686-nptl-linux-gnu-gcc (crosstool-NG 1.20.0) 4.7.4
    > $ echo '#include <glib-object.h>' | i686-nptl-linux-gnu-gcc -x c -I
    staging/usr/include/glib-2.0 -I staging/usr/lib/glib-2.0/include -Wall
    -Werror -c - -o /tmp/foo.o
    > In file included from
    staging/usr/include/glib-2.0/gobject/gbinding.h:29:0,
    >                  from staging/usr/include/glib-2.0/glib-object.h:23,
    >                  from <stdin>:1:
    > staging/usr/include/glib-2.0/gobject/gobject.h: In function
    'g_set_object':
    > staging/usr/include/glib-2.0/gobject/gobject.h:725:5: error: value
    computed is not used [-Werror=unused-value]
    > cc1: all warnings being treated as errors

    This error has been added by commit
    3fae39a5d742afe73741f5fd7aa24e3ae8182f06
    So enable the new g_set_object definition only if gcc >= 4.8

    Fixes:
     -
     http://autobuild.buildroot.net/results/b29a2f868438a2210873ea72f491db63175848be

    Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

    https://bugzilla.gnome.org/show_bug.cgi?id=795138

 gobject/gobject.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit d060ab922ed9ec3591ce605e8412f7d2b6fae539
Author: Philip Withnall <withnall@endlessm.com>
Date:   Mon Feb 26 20:03:02 2018 +0000

    tests: Fix a minor memory leak in the GFileMonitor tests

    Signed-off-by: Philip Withnall <withnall@endlessm.com>

    https://bugzilla.gnome.org/show_bug.cgi?id=755721

 gio/tests/testfilemonitor.c | 1 +
 1 file changed, 1 insertion(+)

commit 21d761b4e2ccfb8396223610e8306bc3ee7bfb60
Author: Philip Withnall <withnall@endlessm.com>
Date:   Mon Feb 26 11:55:03 2018 +0000

    tests: Add a GFileMonitor test for G_FILE_MONITOR_WATCH_HARD_LINKS

    Add a test for monitoring an existing local file, with the
    WATCH_HARD_LINKS flag specified. This would previously cause a crash;
    now it doesn’t.

    This test contains a FIXME where I suspect we should be getting some
    additional file change notifications from changes made through
    the hard
    link; this requires further follow up and probably further fixes
    to our
    inotify backend.

    Signed-off-by: Philip Withnall <withnall@endlessm.com>

    https://bugzilla.gnome.org/show_bug.cgi?id=755721

 config.h.meson              |   3 +
 config.h.win32.in           |   3 +
 configure.ac                |   2 +-
 gio/tests/testfilemonitor.c | 159
 ++++++++++++++++++++++++++++++++++++++++++++
 meson.build                 |   1 +
 5 files changed, 167 insertions(+), 1 deletion(-)

commit b326c23d633c380eaff16c50c815f867d4f37983
Author: Philip Withnall <withnall@endlessm.com>
Date:   Mon Feb 26 13:35:07 2018 +0000

    inotify: Further fixes for hard link monitoring support

    This gets the G_FILE_MONITOR_WATCH_HARD_LINKS flag to the state
    where it
    doesn’t cause crashes, and essentially acts as a no-op. It will
    not yet
    actually monitor for changes made via hard links.

    Signed-off-by: Philip Withnall <withnall@endlessm.com>

    https://bugzilla.gnome.org/show_bug.cgi?id=755721

 gio/glocalfilemonitor.c      | 36 ++++++++++++++++++++++++------------
 gio/inotify/inotify-helper.c |  2 --
 2 files changed, 24 insertions(+), 14 deletions(-)

commit 3f66ab2ede4d637c7c9bf4c0ee7a98d062994cd0
Author: Ryan Lortie <desrt@desrt.ca>
Date:   Tue Sep 29 16:48:29 2015 -0400

    inotify: fix segfault on watching hard links

    The call to _start() fills in the dirname, basename, and filename
    arguments according to the following rules:

      dir watches: dirname filled

      file watches: dirname and basename filled

      hardlink: filename filled

    This doesn't map to how the current inotify backend works very nicely,
    so we need to adjust things a bit when creating our "sub" objects.

    https://bugzilla.gnome.org/show_bug.cgi?id=755721

 gio/inotify/ginotifyfilemonitor.c |  2 +-
 gio/inotify/inotify-sub.c         | 19 +++++++++++++++----
 gio/inotify/inotify-sub.h         |  2 +-
 3 files changed, 17 insertions(+), 6 deletions(-)

commit 78aa070a2432a79edff6d0d98767b00beb7c9a00
Author: Stas Solovey <whats_up@tut.by>
Date:   Thu Apr 12 11:45:34 2018 +0000

    Update Russian translation

 po/ru.po | 36 ++++++++++++++++++------------------
 1 file changed, 18 insertions(+), 18 deletions(-)

commit f403e167978faf78f86aff7de9b14faef7fe9deb
Author: Stas Solovey <whats_up@tut.by>
Date:   Thu Apr 12 11:41:26 2018 +0000

    Update Russian translation

 po/ru.po | 2309
 ++++++++++++++++++++++++++++++++++++++------------------------
 1 file changed, 1430 insertions(+), 879 deletions(-)

commit 1d2e685d90cbebdfcc0b2b2caf6e665c7e93d31d
Author: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Date:   Tue Apr 10 18:55:11 2018 +0200

    gio: fix compilation without F_{S,G}ETPIPE_SZ

    Commit a5778ef7c51044147fe470ea1707dd297f44f880 broke compilation on
    architectures without F_SETPIPE_SZ and F_GETPIPE_SZ such as or1k.
    If those variables are undefined, put back previous behavior, buffer
    size set to 1024 * 64

    Fixes:
     -
     http://autobuild.buildroot.net/results/398490e07343a931b25ca6ab5c90a75d7a073e9f

    (Modified by Philip Withnall <withnall@endlessm.com> to add an
    explanatory comment.)

    Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

    https://bugzilla.gnome.org/show_bug.cgi?id=795133

 gio/gfile.c | 8 ++++++++
 1 file changed, 8 insertions(+)

commit 96904149e20a04066290bc1592469930c2f57ed0
Author: Руслан Ижбулатов <lrn1986@gmail.com>
Date:   Wed Apr 11 11:11:24 2018 +0000

    W32 gstdio: Don't try to get reparse tag unconditionally

    We do not need to use FindFirstFileW() to get a reparse tag if the
    file that is being examined is not a reparse point.

    This is a quick and relatively painless fix for the fact that
    FindFirstFileW() fails on root directories. Since root directories
    are unlikely to be reparse points (is it even possible?), not using
    this function on non-reparse-points just sidesteps the issue.

    https://bugzilla.gnome.org/show_bug.cgi?id=795153

 glib/gstdio.c | 23 ++++++++++++++---------
 1 file changed, 14 insertions(+), 9 deletions(-)

commit 9200ba1ea76e8c1595143d89c9851f679dc89355
Author: Руслан Ижбулатов <lrn1986@gmail.com>
Date:   Wed Apr 11 12:48:06 2018 +0000

    W32 gstdio: don't close fd handle

    If a handle was obtained from a fd that we got from up the stack,
    we shouldn't call CloseHandle() on it in case of an error.

    This is a bug. Luckily, it happens only on the error codepath, so,
    hopefully, no one had hit it yet.

 glib/gstdio.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

commit 262a0a833d48f27b8dabf0d967650a35c3953d11
Author: Matej Urbančič <mateju@svn.gnome.org>
Date:   Tue Apr 10 17:54:11 2018 +0200

    Updated Slovenian translation

 po/sl.po | 52 ++++++++++++++--------------------------------------
 1 file changed, 14 insertions(+), 38 deletions(-)

commit 6106d18ae6b426a7d94fc9ec5129d5319016dfae
Author: Ryan Schmidt <gnome@ryandesign.com>
Date:   Thu Mar 15 21:16:00 2018 +0000

    gio: Fix build on OS X < 10.9

    Commit 170466db accidentally partially reverted commit d1a03bc7.
    Reinstate the missing check for OS X 10.9.

    The Meson build does not have this problem.

    https://bugzilla.gnome.org/show_bug.cgi?id=794380

 gio/Makefile.am | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

commit e4227408b2c3f2d36bdfb6f40e373de64b2bca69
Author: Iain Lane <iain@orangesquash.org.uk>
Date:   Thu Mar 29 11:39:15 2018 +0100

    tests/network-monitor: Always use the dummy proxy resolver

    If glib-networking is installed and built with libproxy support, this
    test will use it. If a proxy is set in the environment, we might get
    correctly told to go through it for certain accesses. However,
    this isn't
    going to work, because the testsuite monkeys with the network
    monitor to
    tell it that all addresses - including the proxy - aren't reachable.

    We're trying to check if adding networks to a GNetworkMonitor works in
    general. Proxies just get in the way here, so let's use the built in
    dummy proxy resolver which just tells us that all URLs are directly
    accessible.

    https://bugzilla.gnome.org/show_bug.cgi?id=794801

 gio/tests/network-monitor.c | 10 ++++++++++
 1 file changed, 10 insertions(+)