https://github.com/GNOME/glib

sort by:
Revision Author Date Message Commit Date
1161ac3 Merge branch 'wip/oholy/bind-mounts-stable' into 'glib-2-58' gunixmounts: Filter out mounts with device path that was repeated See merge request GNOME/glib!365 23 October 2018, 01:53:30 UTC
a03083e Meson: Fix linking of gdbus-peer test 19 October 2018, 14:34:02 UTC
dcc12e0 Merge branch 'cherry-pick-5c22b2dd' into 'glib-2-58' Merge branch '1bit-emufutex-slow' into 'master' See merge request GNOME/glib!408 19 October 2018, 14:04:34 UTC
4aca783 Merge branch '1bit-emufutex-slow' into 'master' meson: Mark 1bit-emufutex test as slow See merge request GNOME/glib!406 (cherry picked from commit 5c22b2ddde21c9080d1a9a090e1945f7a1d4c5f2) 442b54f0 meson: Mark 1bit-emufutex test as slow 19 October 2018, 13:37:58 UTC
8c6ec76 Merge branch '1543-glib-2-58-backports' into 'glib-2-58' Resolve "Backport recent Meson/pkg-config/test fixes to glib-2-58" See merge request GNOME/glib!392 19 October 2018, 13:37:17 UTC
ed88b23 gunixmounts: Filter out mounts with device path that was repeated libmount-based implementation doesn't filter out mounts with device path that was repeated as it is done with mntent-based implementation. It causes problems to our volume monitors which are not able to handle multiple mounts for one device path properly without additional API. Let's filter out the same mounts as are filtered out with mntent-based implementation. This is intended only for stable branches to prevent current issues. https://gitlab.gnome.org/GNOME/glib/issues/1271 17 October 2018, 12:29:45 UTC
34a3ba7 m4macros: Fix detection of glib-2.0 alone We unconditionally appended ">= $min_glib_version" to the modules to look for, even though we had already included "glib-2.0 >= $min_glib_version" in our list. When requesting additional modules, this was fine, for example AM_PATH_GLIB_2_0([2.58], [:], [:], [gobject gio]) ended up asking pkg-config for glib-2.0 >= 2.58 gobject-2.0 gio-2.0 >= 2.58 which is redundant (since they all share a version number) but otherwise OK. However, AM_PATH_GLIB_2_0([2.58], [:], [:], []) ended up asking pkg-config for glib-2.0 >= 2.58 >= 2.58 which is not OK; the second ">=" was parsed as a bizarrely-named package to check for, and obviously few people have ">=.pc" installed. Signed-off-by: Simon McVittie <smcv@collabora.com> Fixes: 4bb16f48 "m4macros: Allow information from pkg-config to be overridden" 11 October 2018, 14:19:52 UTC
19c9081 m4macros: Allow information from pkg-config to be overridden By using PKG_CHECK_VAR, we declare $GLIB_COMPILE_SCHEMAS, $GLIB_GENMARSHAL, $GOBJECT_QUERY, $GLIB_MKENUMS and $GLIB_COMPILE_RESOURCES as Autoconf "precious variables" with AC_ARG_VAR, similar to $PKG_CONFIG and $CC, so that they can be put on a configure command line: ./configure GLIB_COMPILE_RESOURCES=my-glib-compile-resources If they are set to a non-empty value, PKG_CHECK_VAR will use that instead of auto-detecting from pkg-config, so that builders can override them, for example when cross-compiling. Similarly, use the standard PKG_CHECK_MODULES macro to get GLib's CFLAGS and LIBS. It's possible that most of the rest of each macro can also disappear, but for the moment I've given them the benefit of the doubt. This does result in printing "checking for GLIB" twice (once for PKG_CHECK_MODULES and once for GLib's custom checks), but if you're using Autotools, you probably don't have a strong objection to overly verbose output. Signed-off-by: Simon McVittie <smcv@collabora.com> 11 October 2018, 14:19:52 UTC
55b17dc Autotools: Move libmount from Libs.private to Requires.private libmount depends on libblkid, so if we statically link a trivial executable to GIO, we need to pull in both libmount and libblkid. Linking with -lmount is not enough to achieve that, but recursing into mount.pc is. This makes the Autotools build a bit more like the Meson build, which already puts mount in Requires.private. Signed-off-by: Simon McVittie <smcv@collabora.com> 11 October 2018, 00:37:49 UTC
c9f5eef Autotools: Always run glib-genmarshal, even if cross-compiling glib-genmarshal is now written in Python rather than C, so we can always run it directly, even if we're cross-compiling for an architecture whose binaries we can't run. This matches the behaviour of the Meson build system. Fixes: https://gitlab.gnome.org/GNOME/glib/issues/1546 Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908334 Signed-off-by: Simon McVittie <smcv@collabora.com> 11 October 2018, 00:37:24 UTC
6f3241f Fix build failure on systems without spawn.h 10 October 2018, 17:51:07 UTC
d757bd8 Meson: Extract objects from convenience libraries to link them This avoids the convenience library being treated as though it was an installed static library (objects not included in the dependent static library, and convenience library being listed in the pkg-config metadata), both of which would make static linking impossible. This is a workaround for meson not having https://github.com/mesonbuild/meson/pull/3939 merged yet. Fixes: https://gitlab.gnome.org/GNOME/glib/issues/1536 Signed-off-by: Simon McVittie <smcv@collabora.com> 10 October 2018, 17:51:07 UTC
c733f16 Tests: Mark printf wrappers with G_GNUC_PRINTF If we tell clang that we're passing the arguments on to a compatible printf call, it can see that we're doing it right, and won't warn us about -Wformat-nonliteral. This follows up from commit abac67c0. Signed-off-by: Simon McVittie <smcv@collabora.com> 10 October 2018, 17:51:07 UTC
067d4b4 Meson: appinfo tests are racy if run in parallel 10 October 2018, 17:51:07 UTC
41bd74d Generate gtester-report from .in file Previously, it was installed unmodified by the Meson build system. We don't need to define @bindir@, because gtester-report never actually referred to it. We also don't need a definition of GTESTER_REPORT for use by GLib itself, because its last use was removed in 2013 (https://bugzilla.gnome.org/show_bug.cgi?id=709995). Fixes: https://gitlab.gnome.org/GNOME/glib/issues/1544 Signed-off-by: Simon McVittie <smcv@collabora.com> 10 October 2018, 17:51:07 UTC
e704c23 Spelling: Fix spelling of "interpreted" Detected by Debian's Lintian tool. Signed-off-by: Simon McVittie <smcv@collabora.com> 10 October 2018, 17:51:07 UTC
6c806c2 Spelling: avoid the "allows to" pattern This is detected by Debian's Lintian tool, which suggests "allows one to" as a replacement. I've rephrased the documentation in question to avoid both of those. Signed-off-by: Simon McVittie <smcv@collabora.com> 10 October 2018, 17:51:07 UTC
31d2273 Spelling: Fix spelling of "unknown" Signed-off-by: Simon McVittie <smcv@collabora.com> 10 October 2018, 17:51:07 UTC
cc3d955 Spelling: Fix spelling of "constructed" Signed-off-by: Simon McVittie <smcv@collabora.com> 10 October 2018, 17:51:07 UTC
ff2b5d3 Spelling: Fix spelling of "similarly" Detected by Debian's Lintian tool. Signed-off-by: Simon McVittie <smcv@collabora.com> 10 October 2018, 17:51:07 UTC
a915c7b Spelling: Fix a common en_FR spelling of "information" Detected by Debian's Lintian tool. Signed-off-by: Simon McVittie <smcv@collabora.com> 10 October 2018, 17:51:07 UTC
8e62a5d Spelling: fix spelling of specify Detected by Debian's Lintian tool. Signed-off-by: Simon McVittie <smcv@collabora.com> 10 October 2018, 17:51:06 UTC
419d823 Spelling: fix "every time" Detected by Debian's Lintian tool. Also fix the spelling of "linking" in one error message. Signed-off-by: Simon McVittie <smcv@collabora.com> 10 October 2018, 17:51:06 UTC
ae5bca2 Meson: Do not run tests/refcount with --tap This is a partial revert of a change introduced in cbc7fbbf7. 10 October 2018, 17:51:06 UTC
59f8519 meson: Run build-time tests with --tap where supported This makes it easier to debug test failures, by ensuring that g_debug() and g_test_message() are printed as TAP diagnostics. Fixes: https://gitlab.gnome.org/GNOME/glib/issues/1528 Signed-off-by: Simon McVittie <smcv@collabora.com> 10 October 2018, 17:51:06 UTC
7723eba Meson: Install timeloop-closure test 10 October 2018, 17:51:06 UTC
2c5bc25 Meson: doc: fix cross references 10 October 2018, 17:51:06 UTC
ac7534f Meson: Run in TAP mode installed tests that support it 10 October 2018, 17:51:06 UTC
aa02dac Meson: define G_HAVE_GROWING_STACK to 0 or 1 10 October 2018, 17:51:06 UTC
9cde3b2 Remove unnecessary +x permissions None of these files starts with a #! line, and they are not native binary executables, so if a user attempts to execute them as a program, Unix shells will run them as /bin/sh scripts. This is not going to end well, since none of them are shell scripts (the gio bash completion is for bash, which is not a lowest-common-denominator POSIX shell, and in any case is designed to be sourced rather than executed). Fixes: #1539 Signed-off-by: Simon McVittie <smcv@collabora.com> 10 October 2018, 17:51:06 UTC
5038346 Tests: Fix -Wformat-nonliteral causing build failure with clang 10 October 2018, 17:51:06 UTC
e459e7b tests W32: ifdef a variable not used on Windows 10 October 2018, 17:51:06 UTC
063148e tests W32: Move timeloop test to the non-Windows section It just doesn't work on Windows, and that can't be fixed with a quick patch. 10 October 2018, 17:51:06 UTC
c6d1f68 tests W32: ugly fix for sscanf() format As we recently established, G_G*_FORMAT macros are for glib functions *only*. It's not guaranteed that they will work for C runtime printf() or scanf() variants, and indeed - in this case they do not (GCC thinks that MSVCRT sscanf() requires %I64 prefix for 64-bit values; whether that is true or not is irrelevant at this point - we need to make the werror go away). 10 October 2018, 17:51:06 UTC
c5ad1ca tests W32: include process.h for getpid() At least, MinGW has POSIX names. No idea if this works in MSVC. 10 October 2018, 17:51:06 UTC
b22f3bf tests W32: Fix Windows values casting LPARAM is LONG_PTR which is the same as INT_PTR on Windows. WPARAM is UINT_PTR. HWND is a pointer. (%p prints pointers without 0x prefix, hence the extra 0x). 10 October 2018, 17:51:06 UTC
12fe2cb tests W32: Cast the MSG struct as (gchar *) for g_io_channel_read 10 October 2018, 17:51:06 UTC
ba62f9a Rename cxx-test.C to cxx-test.cpp Meson checks file extension case-insentively, and compiles ".C" as C source instead of C++. 10 October 2018, 17:51:06 UTC
8d7f506 Meson: build and install remaining tests 10 October 2018, 17:51:06 UTC
100a853 Meson: Fix missing files when installing tests Closes #1527 10 October 2018, 17:51:06 UTC
faaf0fb tests: Mark two more tests as slow These keep on taking just longer than 30s on my local machine when run in parallel with the rest of the tests (i.e. with `ninja test`). Testing them individually, they do terminate correctly. Signed-off-by: Philip Withnall <withnall@endlessm.com> 10 October 2018, 17:51:06 UTC
6e1311c gio: automake: Add libgmodule dependency Otherwise I get following compile error: libtool: link: /home/builduser/toolchains/linux/tc/2017-12/x86-ncp-linux-gnu/bin/i686-ncp-linux-gnu-gcc -Wall -Wstrict-prototypes -Wmisleading-indentation -Wno-bad-function-cast -Werror=declaration-after-statement -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format=2 -O2 -Wall -pipe -Wformat -g -fstack-protector-strong -fPIC -fno-strict-aliasing -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-rpath-link=/home/builduser/workspaces/rws_trunk_linux_x86_build_shared-fips/build/3p/linux/x86/install/zlib/lib -Wl,-rpath-link=/home/builduser/workspaces/rws_trunk_linux_x86_build_shared-fips/build/3p/linux/x86/install/libffi/lib -o .libs/gio gio-tool.o gio-tool-cat.o gio-tool-copy.o gio-tool-info.o gio-tool-list.o gio-tool-mime.o gio-tool-mkdir.o gio-tool-monitor.o gio-tool-mount.o gio-tool-move.o gio-tool-open.o gio-tool-rename.o gio-tool-remove.o gio-tool-save.o gio-tool-set.o gio-tool-trash.o gio-tool-tree.o -L/home/builduser/workspaces/rws_trunk_linux_x86_build_shared-fips/build/3p/linux/x86/install/zlib/lib -L/home/builduser/workspaces/rws_trunk_linux_x86_build_shared-fips/build/3p/linux/x86/install/libffi/lib ./.libs/libgio-2.0.so ../gobject/.libs/libgobject-2.0.so ../glib/.libs/libglib-2.0.so -Wl,-rpath -Wl,/home/builduser/workspaces/rws_trunk_linux_x86_build_shared-fips/build/3p/linux/x86/install/glib/lib /home/builduser/toolchains/linux/tc/2017-12/x86-ncp-linux-gnu/bin/../lib/gcc/i686-ncp-linux-gnu/6.3.0/../../../../i686-ncp-linux-gnu/bin/ld: warning: libgmodule-2.0.so.0, needed by ./.libs/libgio-2.0.so, not found (try using -rpath or -rpath-link) ./.libs/libgio-2.0.so: undefined reference to `g_module_error' ./.libs/libgio-2.0.so: undefined reference to `g_module_close' ./.libs/libgio-2.0.so: undefined reference to `g_module_open' ./.libs/libgio-2.0.so: undefined reference to `g_module_supported' ./.libs/libgio-2.0.so: undefined reference to `g_module_symbol' collect2: error: ld returned 1 exit status Makefile:2300: recipe for target 'gio' failed Signed-off-by: Bernhard Walle <bernhard@bwalle.de> 10 October 2018, 17:51:06 UTC
6e75d3c test_internal_enhanced_stdio: don't use g_assert() g_assert() can be disabled, use more specific assertion macros. 10 October 2018, 17:51:06 UTC
13c088d W32: extend the g-file-info test with new DOS attributes 10 October 2018, 17:51:06 UTC
a2375b8 W32: new GFileInfo attributes G_FILE_ATTRIBUTE_DOS_IS_MOUNTPOINT allows mountpoints (NTFS reparse points with IO_REPARSE_TAG_MOUNT_POINT tag) to be told apart from symlinks (NTFS reparse points with IO_REPARSE_TAG_SYMLINK tag), even though both are reported by glib as "symlinks". G_FILE_ATTRIBUTE_DOS_REPARSE_POINT_TAG allows the exact reparse tag value to be obtained by the user. This way even more exotic reparse points can be identified and handled by the user (glib itself currently has no code to work with any reparse points that are not symlinks or mountpoints). 10 October 2018, 17:51:06 UTC
01855d2 W32: tighten access rights requested to read symlink According to http://blog.kalmbach-software.de/2008/02/28/howto-correctly-read-reparse-data-in-vista/ we only need FILE_READ_EA, and should also use wider share flags. 10 October 2018, 17:51:06 UTC
cb1a4e0 W32: test the private path-stripping function 10 October 2018, 17:51:06 UTC
2a80628 W32: Don't always strip path prefixes Extended path prefix looks like "\\?\", and NT object path prefix looks like "\??\". Strip them only if they are followed by a character (any character) and a colon (:), indicating that it's a DOS path with a drive. Otherwise stripping such prefix might result in a patch that looks like a relative path. For example, "\\?\Volume{GUID}\" becomes "Volume{GUID}\", which is a valid directory name. Currently it's up to the user to make sense of such paths. 10 October 2018, 17:51:06 UTC
d72d141 Enable GIO tests on Windows 1) Remove the non-Windows-only condition for subdir('tests'). 2) Add libiphlpapi, libws2_32 and libsecur32 deps, needed for W32 tests. 3) Remove the -no-undefined argument (gcc doesn't understand it, it *does* understand -Wl,-no-undefined; either way, the test compiles without this argument just fine; maybe meson adds it by itself - you can hardly build shared modules without it). 4) Add or fix a number of includes 5) Disable gdbus-objectmanager tests when building with MSVC (right now these tests don't work on Windows anyway, so the fact that MSVC can't even build them properly is irrelevant; most likely gdbus-codegen needs changes to put _GLIB_EXTERN before each function) 10 October 2018, 17:51:06 UTC
400cec2 Install m4 macros unconditionally Partial revert of commit a7a6449f4d63357bf3a66140e9fb3ccb18611c0b. Checking for the availability of m4 for installing m4 macro files creates an implicit dependency on m4 even if GLib does not need it; this prevents building GLib and then installing Autotools in order to build a project that depends on GLib. Closes #1520 10 October 2018, 17:51:06 UTC
c1f78a5 build: Drop pointless -Wformat-security warning flag We already set -Wformat=2, which implies -Wformat-security, so there’s no need to test for and set -Wformat-security separately. The test for -Wformat-security never worked anyway, since gcc complains if it’s specified without also setting -Wformat to some value. The complaint causes configure.ac/meson.build to assume the option doesn’t work. Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/656 10 October 2018, 17:51:06 UTC
60adc1e build: Drop AC_C_CONST from configure.ac Any compiler we care about now supports the `const` keyword, so we no longer need to check for it. autoconf has recommended this macro is obsolete: https://www.gnu.org/software/autoconf/manual/autoconf-2.60/html_node/C-Compiler.html#index-AC_005fC_005fCONST-755 Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/1313 10 October 2018, 17:51:06 UTC
540fd15 glib: Remove remaining references to __int64 This is a follow-up to 7e821441c482917e54435a07893272d87d3ad9e5 and e154e3325eb7274b8164f8d7a5e0f335646c2bb7 removing some remaining references to __int64 which are no longer necessary. Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/1313 10 October 2018, 17:51:06 UTC
7df0977 build: Remove SIZEOF___INT64 definition from meson.build This was a leftover from use of the __int64 type, which was removed recently in commit 7e821441c482917e54435a07893272d87d3ad9e5. Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/1313 10 October 2018, 17:51:06 UTC
e42d5da build: Stop defining STDC_HEADERS This was previously defined by the AC_HEADER_STDC macro in configure.ac, but we don’t use that any more. Nothing in GLib depends on this macro, and neither does anything in my /usr/include which we might care about. The autoconf documentation for AC_HEADER_STDC says it’s deprecated: https://www.gnu.org/software/autoconf/manual/autoconf-2.67/html_node/Particular-Headers.html#index-AC_005fHEADER_005fSTDC-621 Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/1313 10 October 2018, 17:51:06 UTC
e17be33 build: Drop unused HAVE_DLFCN_H definition I can’t see this being used anywhere in GLib, or in my /usr/include directory. I’m also not sure how configure.ac ends up defining it — it’s certainly as a side-effect of something, and not deliberate. Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/1313 10 October 2018, 17:51:06 UTC
f85c462 build: Check for bind_textdomain_codeset() properly Previously we weren’t checking for it in meson.build (but were checking for it in configure.ac, courtesy of glib-gettext.m4). Roughly emulate the checks from glib-gettext.m4, checking for bind_textdomain_codeset() in whichever libintl implementation we found ngettext() in. meson.build still doesn’t implement the full set and order of checks in glib-gettext.m4; there’s still a FIXME about that in meson.build. Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/1313 10 October 2018, 17:51:06 UTC
bdc37e3 build: Define GLIB_USING_SYSTEM_PRINTF properly Previously it was hard-coded to true, rather than being based on the calculations actually made by meson.build. Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/1313 10 October 2018, 17:51:06 UTC
d0e979b build: Check for Unix98 positional parameter support in printf() This is equivalent to the AC_FUNC_PRINTF_UNIX98 macro which we use in configure.ac. There may still be some obscure Unix platforms which don’t natively support positional parameters, 20 years on. Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/1313 10 October 2018, 17:51:06 UTC
3f9a922 build: simplify alloca checks. See #1313 The goal of this commit is to reduce differences between the autotools and meson build. With autotools AC_FUNC_ALLOCA was used which defines HAVE_ALLOCA_H, HAVE_ALLOCA, C_ALLOCA. meson tried to replicate that with has_function() but alloca can be a macro and and is named _alloca under Windows. Since we require a working alloca anyway and only need to know if the header exists replace AC_FUNC_ALLOCA with a simple AC_CHECK_HEADERS. There is still one user of HAVE_ALLOCA in the embedded gnulib, but since alloca is always provided through galloca.h just force define HAVE_ALLOCA there and add a comment. The docs were mentioning alloca as an example for cross compiling. Since that variable no longer exists now replace it with another one. 10 October 2018, 17:51:06 UTC
fc7b8e8 Update Friulian translation 29 September 2018, 14:51:23 UTC
a579ac9 Merge branch 'stable-ci' into 'glib-2-58' ci: Use a docker image for stable branch See merge request GNOME/glib!346 28 September 2018, 14:30:49 UTC
21da53a ci: Use a docker image for stable branch The master docker image will eventually use a new meson version, but we want to ensure stable branch still works on old version. 24 September 2018, 14:05:15 UTC
a9f5a6f 2.58.1 Signed-off-by: Philip Withnall <withnall@endlessm.com> 21 September 2018, 14:21:06 UTC
2a7d4d2 Merge branch 'glib-2-58-309-codegen-punning' into 'glib-2-58' codegen: Change pointer casting to remove type-punning warnings See merge request GNOME/glib!318 17 September 2018, 13:12:47 UTC
ae9bb1e Merge branch 'glib-2-58-1513-icon-docs' into 'glib-2-58' Backport to glib-2-58: Fix g_icon_to_string() regression (doc inconsistency) See merge request GNOME/glib!330 17 September 2018, 13:11:31 UTC
ac1b680 Merge branch 'glib-2-58-315-pc-paths' into 'glib-2-58' Use absolute paths in pkg-config files See merge request GNOME/glib!329 17 September 2018, 10:35:09 UTC
ad26f4c Fix g_icon_to_string() regression (doc inconsistency). g_icon_new_for_string() docs states that it should return a single name when created with a single name. I add a second condition to this case: the themed icon must not include default fallbacks (i.e. it must not have been created with `g_themed_icon_new_with_default_fallbacks()`). Otherwise the return value of `g_icon_new_for_string()` would not recreate the same icon list when passed to `g_icon_new_for_string()` (which would be another documentation inconsistency). g_icon_new_for_string() is now back to old behavior for this specific case. I also revert the unit test for this case, and add a new unit test when using g_themed_icon_new_with_default_fallbacks() with a single name as well. Closes #1513. 17 September 2018, 10:33:55 UTC
e7a7c9b Use absolute paths in pkg-config files According to https://www.bassi.io/articles/2018/03/15/pkg-config-and-paths/, pkg-config files should use absolute paths in variables. This fixes commit 47692845c0a062a76f99b5de125c5eafa4556847. Closes #1521 17 September 2018, 09:56:10 UTC
d89e862 Merge branch 'glib-2-58-317-xdg-desktop-portal-autostart' into 'glib-2-58' Backport “Autostart xdg-desktop-portal if needed” to glib-2-58 See merge request GNOME/glib!321 13 September 2018, 14:19:24 UTC
d0660ff Merge branch 'glib-2-58-313-network-monitor-netlink-fixes' into 'glib-2-58' Backport GNetworkMonitorNetlink fixes from !313 to glib-2-58 See merge request GNOME/glib!324 13 September 2018, 14:14:02 UTC
7e413f8 gnetworkmonitornetlink: Close the socket after disconnecting its GSources `read_netlink_messages()` is the callback attached to the netlink socket (G_IO_IN). It calls `g_socket_receive_message()`. There is a race condition that if the socket is closed while there is a pending call, we will try to receive on a closed socket, which fails. To avoid this, we switch the order of the operations around: first destroy the source and then close the socket. 13 September 2018, 13:10:39 UTC
8b26ad2 gnetworkmonitornetlink: Don't check if a passed-in GError ** is NULL This is not a correct way to check if `g_socket_new_from_fd()` failed. Instead just see if it returned `NULL` itself. This was preventing the netlink monitor from being initialised. Closes #1518 13 September 2018, 13:10:39 UTC
d8d3c81 Updated Czech translation 13 September 2018, 12:00:30 UTC
ce2e543 Autostart xdg-desktop-portal if needed This is a speculative fix for epiphany#533, which we think might be caused by xdg-desktop-portal not ever being started. This service is started on-demand, not automatically. 13 September 2018, 09:07:11 UTC
b3bad4a codegen: Change pointer casting to remove type-punning warnings The existing code was generating code with undefined results that modern compilers warn about: accounts-generated.c:204:23: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] (GDBusArgInfo **) &_accounts_accounts_method_info_list_cached_users_OUT_ARG_pointers, 12 September 2018, 22:34:43 UTC
c3c059e Update Greek translation 05 September 2018, 22:10:06 UTC
9d41491 Merge branch 'cherry-pick-68a4e273' into 'glib-2-58' Document that GTimeVal is subject to the year 2038 problem on 32-bit systems See merge request GNOME/glib!306 05 September 2018, 13:27:22 UTC
37af51e Document that GTimeVal is subject to the year 2038 problem on 32-bit systems It might not be immediately obvious that this is the case. Let's record it in the description of `GTimeVal` itself and also in `g_time_val_from_iso8601`. We also drop an incorrect statement in the documentation for `g_time_val_from_iso8601` stating that years up to 3000 were supported; this is also not true for the same reason. Related: #1509 (cherry picked from commit 68a4e273b443ad79a3cd392d464390ab6a3fed2e) 05 September 2018, 13:15:00 UTC
f1e272e Merge branch '277-command-v-not-which-glib-2-58' into 'glib-2-58' Backport `command -v` vs `which` changes to glib-2-58 See merge request GNOME/glib!288 05 September 2018, 10:12:41 UTC
5e9c2a5 Merge branch 'glib-2-58-backports' into 'glib-2-58' GLib 2.58 backports of various small patches See merge request GNOME/glib!298 05 September 2018, 10:10:55 UTC
7086bae Merge branch 'cherry-pick-f697f6aa' into 'glib-2-58' tests/timer: Skip test_timeval_to_iso8601_overflow if we can't overflow a GTimeVal See merge request GNOME/glib!301 04 September 2018, 09:58:38 UTC
51e7219 tests/timer: Skip test_timeval_to_iso8601_overflow if we can't overflow a GTimeVal On 32 bit systems, the size of a long might be the same as the size of an int. In that case, we won't be able to get an overflow when converting from a GTimeVal to a time_t. Skip the test for this in that case. Closes #1509 (cherry picked from commit f697f6aa08dc5499ae1c5c9177976cc62d19a998) 04 September 2018, 09:49:34 UTC
d62f7cb meson: fix typo 03 September 2018, 12:19:51 UTC
a8babc7 portal network monitor: Always emit changed signal on changed The ::network-changed signal is documented to indicate any change in network configuration, which doesn't necessarily imply a property change - additional services becoming available after connecting to a VPN comes to mind for instance. In order to match the "native" network monitor's behavior, always emit the signal when it's in response to the 'changed' D-Bus signal. Also emit the signal unconditionally when loading the initial property values, to allow clients to differentiate between "offline" meaning "offline" and "offline" meaning "uninitialized". 03 September 2018, 12:14:47 UTC
f042610 build: fix installation dir of glib-gettextize 03 September 2018, 12:10:58 UTC
b8a4754 gspawn: Fix build on systems without O_CLOEXEC Fixes typo introduced in 4afe429d7ce4d813e0b263fd3eab9e543f11d2a6. See https://gitlab.gnome.org/GNOME/glib/issues/1488 03 September 2018, 11:54:02 UTC
afbda14 gio: Don't redefine GKqueueFileMonitor Fixes build on old compilers that don't allow type redefinitions. Closes: https://gitlab.gnome.org/GNOME/glib/issues/1506 03 September 2018, 11:49:16 UTC
6a3fb34 Update Greek translation 03 September 2018, 09:05:04 UTC
3aefb47 Updated Danish translation 02 September 2018, 21:21:43 UTC
5afb4ce Update Swedish translation 02 September 2018, 20:07:32 UTC
3392d7c Update Latvian translation 02 September 2018, 16:57:52 UTC
1d6909c Update Hungarian translation 01 September 2018, 22:19:28 UTC
2a64690 Update Brazilian Portuguese translation 01 September 2018, 15:22:22 UTC
40ee8da Use "command -v" instead of "which" The behavior of "which" is not standardized by POSIX. Some old implementations print their error messages to stdout instead of stderr, and don't return a nonzero exit code when they fail to find the given program. "command -v" on the other hand is in POSIX (optional in 2004 and required as of 2008). Remove otherwise-unused variables AUTORECONF and GTKDOCIZE. 31 August 2018, 11:41:32 UTC
c138b98 2.58.0 Signed-off-by: Philip Withnall <withnall@endlessm.com> 30 August 2018, 17:11:13 UTC
90815c1 Merge branch 'autotools-config.h' into 'master' ci: Include config.h in autotools output artifacts See merge request GNOME/glib!281 30 August 2018, 14:25:14 UTC
f4b3e62 Merge branch 'ci-no-coverage-on-dist' into 'master' ci: Disable the coverage CI job when running dist on a release See merge request GNOME/glib!284 30 August 2018, 14:24:35 UTC
3ced28d ci: Disable the coverage CI job when running dist on a release It fails because dist-job (correctly) doesn’t build with the code coverage CFLAGS enabled. Leave coverage to be generated on master and development branches. See this pipeline for an example of when it fails: https://gitlab.gnome.org/GNOME/glib/pipelines/26349 Signed-off-by: Philip Withnall <withnall@endlessm.com> 30 August 2018, 12:51:59 UTC
bb6eb8c Merge branch 'nirbheek/g-module-suffix-macos' into 'master' meson: Always set G_MODULE_SUFFIX to `so` on macOS See merge request GNOME/glib!280 30 August 2018, 12:44:58 UTC
back to top