- Oct 04, 2019
-
-
Philip Withnall authored
Signed-off-by: Philip Withnall <withnall@endlessm.com>
-
- Oct 03, 2019
-
-
Ondrej Holy authored
Backport !1134 Fix for file copy permissions to glib-2-62 See merge request GNOME/glib!1142
-
- Oct 02, 2019
-
-
Philip Withnall authored
[2.62] Always build tests if we enabled installed-tests See merge request GNOME/glib!1141
-
Philip Withnall authored
If a copy operation is started with `G_FILE_COPY_TARGET_DEFAULT_PERMS`, don’t create the destination file as private. Instead, create it with the process’ current umask (i.e. ‘default permissions’). This is a partial re-work of commit d8f8f4d6, with input from Ondrej Holy. Signed-off-by: Philip Withnall <withnall@endlessm.com> Fixes: #174
-
Philip Withnall authored
This introduces no functional changes; just reduces duplication in the code a little. Signed-off-by: Philip Withnall <withnall@endlessm.com>
-
Sebastian Dröge authored
[2.62] g_file_info_get_modification_date_time: Calculate in integer domain See merge request GNOME/glib!1140
-
Simon McVittie authored
If we're cross-compiling, the installed-tests are useful even if we can't run them on the build machine: we can copy them to the host machine (possibly via a distro package like Debian's libglib2.0-tests) and run them there. While I'm changing the build-tests condition anyway, deduplicate it. Based on a patch by Helmut Grohne. Bug-Debian: https://bugs.debian.org/941509 Signed-off-by: Simon McVittie <smcv@collabora.com> (cherry picked from commit 42d8e177)
-
Simon McVittie authored
g_date_time_add_seconds() and g_date_time_add_full() use floating-point seconds, which can result in the value varying slightly from what's actually on disk. This causes intermittent test failures in gio/tests/g-file-info.c on Debian i386, where we set a file's mtime to be 50µs later, then read it back and sometimes find that it is only 49µs later than the previous value. I've only seen this happen on i386, which means it might be to do with different floating-point rounding when a value is stored in the 80-bit legacy floating point registers rather than in double precision. g_date_time_add() takes a GTimeSpan, which is in microseconds; conveniently, that's exactly what we get from the GFileInfo. Bug-Debian: https://bugs.debian.org/941547 Signed-off-by: Simon McVittie <smcv@collabora.com> (cherry picked from commit 14609b0b)
-
Ask Hjorth Larsen authored
-
- Sep 26, 2019
-
-
Sebastian Dröge authored
Backport !1125 and !1115 GDateTime parsing fixes to glib-2-62 See merge request GNOME/glib!1127
-
Sebastian Dröge authored
Backport !1043 “gvariant: Handle empty serialisations in get_child_value()” to glib-2-62 See merge request GNOME/glib!1128
-
- Sep 25, 2019
-
-
Philip Withnall authored
When g_variant_get_child_value() is called for a child whose serialisation is an empty byte string (which is possible), `bytes_data` will be non-`NULL`, but `data` may be `NULL`. This results in a negative offset being passed to `g_bytes_new_from_bytes()`, and a critical warning. So if `data` is `NULL`, set it to point to `bytes_data` so the offset is calculated as zero. The actual value of the offset doesn’t matter, since in this situation the size is always zero. An offset of zero is never going to cause problems. Signed-off-by: Philip Withnall <withnall@endlessm.com> Fixes: #1865
-
Philip Withnall authored
It was possible to pass in (for example) an invalid year to g_date_time_new_week(), which would be passed on to g_date_time_new(), which would (correctly) return `NULL` — but then g_date_time_get_week_number() would try to dereference that. Includes a test case. oss-fuzz#17648 Signed-off-by: Philip Withnall <withnall@endlessm.com>
-
Philip Withnall authored
It was possible to pass in (for example) an invalid hour to g_date_time_new_ordinal(), which would be passed on to g_date_time_new(), which would (correctly) return `NULL` — but then g_date_time_new_ordinal() would try to dereference that. Includes some test cases. oss-fuzz#16103 oss-fuzz#17183 Signed-off-by: Philip Withnall <withnall@endlessm.com>
-
- Sep 20, 2019
-
-
Philip Withnall authored
docs: Remove priv pointers from the tutorial example See merge request GNOME/glib!1021
-
Emmanuele Bassi authored
We define `ViewerFile` as a final type with fields directly in the instance structure. This means we don't have a `priv` pointer to dereference.
-
- Sep 15, 2019
-
-
Марко Костић (Marko Kostić) authored
-
- Sep 13, 2019
-
-
Sebastian Dröge authored
Backport !1085 “xdgmime: Prevent infinite loops from badly-formed MIME registrations” to glib-2-62 See merge request GNOME/glib!1103
-
Philip Withnall authored
Signed-off-by: Philip Withnall <withnall@endlessm.com> Closes: #1875
-
Sebastian Dröge authored
Backport !1080 “tests: Fix skipping mkdir-with-parents-permission test” to glib-2-62 See merge request GNOME/glib!1102
-
Sebastian Dröge authored
Backport !1092 “Fix doc build on Windows” to glib-2-62 See merge request GNOME/glib!1101
-
Philip Withnall authored
If the user has `CAP_DAC_OVERRIDE` or similar (for example, if running the tests as root), the `mkdir-with-parents-permission` test is skipped. The check for `CAP_DAC_OVERRIDE` was by creating a subdirectory of the test directory. That subdirectory, however, was never removed, which caused a ‘directory not empty’ error when trying to delete the test directory. Fix that by correctly deleting the subdirectory if skipping the test. Signed-off-by: Philip Withnall <withnall@endlessm.com>
-
Xavier Claessens authored
This is a work around for this Meson bug: https://github.com/mesonbuild/meson/issues/5893 Closes: #1888
-
- Sep 10, 2019
-
-
Milo Casagrande authored
-
- Sep 09, 2019
-
-
A S Alam authored
-
- Sep 08, 2019
-
-
Nirbheek Chauhan authored
Backport to 2.62: gmodule: use dl implementation on macOS See merge request GNOME/glib!1094
-
- Sep 07, 2019
-
-
Tom Schoonjans authored
-
Tom Schoonjans authored
Closes #1887
-
Emin Tufan Çetin authored
-
- Sep 05, 2019
-
-
Philip Withnall authored
Signed-off-by: Philip Withnall <withnall@endlessm.com>
-
Philip Withnall authored
fileinfo: ignore USEC if not available See merge request GNOME/glib!1087
-
Philip Withnall authored
Signed-off-by: Philip Withnall <withnall@endlessm.com>
-
Philip Withnall authored
They provide more detailed failure messages, and aren’t compiled out when building with `G_DISABLE_ASSERT`. Signed-off-by: Philip Withnall <withnall@endlessm.com>
-
Christian Hergert authored
When future porting deprecated code to use g_file_info_get_modification_date_time() we risk a number of breakages because the current implementation also requires the additional use of G_FILE_ATTRIBUTE_TIME_MODIFIED_USEC. This handles that situation gracefully and returns a GDateTime with less precision. Applications that want the additional precision, are already using the additional attribute. (Minor tweaks by Philip Withnall.)
-
Rafael Fontenelle authored
-
- Sep 04, 2019
-
-
Philip Withnall authored
glib.supp: make gobject_init() calloc also of the possible kind See merge request GNOME/glib!1086
-
Claudio Saavedra authored
It's currently marked only as reachable but Valgrind also finds it as possible: ==18842== 96 bytes in 1 blocks are possibly lost in loss record 2,029 of 2,284 ==18842== at 0x4837B65: calloc (vg_replace_malloc.c:762) ==18842== by 0x49614AD: g_malloc0 (gmem.c:129) ==18842== by 0x4A7013B: type_node_any_new_W (gtype.c:439) ==18842== by 0x4A70609: type_node_fundamental_new_W (gtype.c:550) ==18842== by 0x4A7855A: gobject_init (gtype.c:4406) ==18842== by 0x4A78672: gobject_init_ctor (gtype.c:4493)
-
- Sep 03, 2019
-
-
Fabio Tomat authored
-
- Sep 02, 2019
-
-
Philip Withnall authored
garray: Fix reference to GLIB_SIZEOF_INT See merge request GNOME/glib!1084
-
Alexander Larsson authored
This doesn't ever get set. SIZEOF_INT is set though, so use that instead.
-