summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* network monitor portal: update properties initiallynetwork-monitor-fixMatthias Clasen2018-08-161-4/+17
| | | | | With version 2, we need to query the values explicitly. The properties made this automatic.
* Merge branch 'fix-gdbus-unix-address' into 'master'Philip Withnall2018-08-162-0/+2
|\ | | | | | | | | Fix failing tests when G_MESSAGES_DEBUG is set (again) See merge request GNOME/glib!247
| * Fix failing tests when G_MESSAGES_DEBUG is set (again)Xavier Claessens2018-08-162-0/+2
| | | | | | | | | | | | Similar issue was fixed with commit f929d148, but it's happening again. Define G_MESSAGES_DEBUG=all when running CI to ensure we won't regress anymore.
* | Merge branch '1444-install-tests' into 'master'Xavier Claessens2018-08-162-310/+341
|\ \ | | | | | | | | | | | | | | | | | | Resolve "the meson build doesn't support installed tests" Closes #1444 See merge request GNOME/glib!245
| * | Meson: install gio testsXavier Claessens2018-08-161-260/+276
| | |
| * | Meson: install gobject testsXavier Claessens2018-08-151-50/+65
| |/
* | Merge branch '1454-gvdb-corruption' into 'master'Philip Withnall2018-08-169-300/+390
|\ \ | | | | | | | | | | | | | | | | | | gvdb: Fix error handling in gvdb_table_new() Closes #1454 See merge request GNOME/glib!214
| * | gvdb: Fix error handling in gvdb_table_new()Philip Withnall2018-08-134-4/+109
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The documentation was unclear about what error codes would be returned on attempting to open an empty or corrupt GVDB file. Previous versions of the documentation incorrectly said that corrupt GVDB files were considered equivalent to empty ones. A recent commit has clarified the documentation to include its error handling behaviour. Update the two users of GVDB within GLib, GResource and GSettingsSource, to follow this change, and add unit tests for them both. Other users of the GVDB copylib will need to update their copy and make appropriate changes if they have bugs in their handling of this situation. dconf is one example of this. GVDB should be updated from https://gitlab.gnome.org/GNOME/gvdb. Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/1454
| * | gsettingsschema: Port to new GVDB APIPhilip Withnall2018-08-131-4/+4
| | | | | | | | | | | | | | | | | | This should introduce no functional changes. Signed-off-by: Philip Withnall <withnall@endlessm.com>
| * | gresource: Port to new GVDB APIPhilip Withnall2018-08-131-8/+2
| | | | | | | | | | | | | | | | | | This should introduce no functional changes. Signed-off-by: Philip Withnall <withnall@endlessm.com>
| * | glib-compile-schemas: Fix a minor memory leakPhilip Withnall2018-08-131-0/+1
| | | | | | | | | | | | Signed-off-by: Philip Withnall <withnall@endlessm.com>
| * | Merge remote-tracking branch 'gvdb/master' into update-gvdbPhilip Withnall2018-08-134-285/+275
| |\ \ | | | | | | | | | | | | Minor merge conflicts in gvdb-reader.c with the documentation.
| | * | docs: Clarify error values for empty files when loadingPhilip Withnall2018-08-131-1/+8
| | | | | | | | | | | | | | | | Signed-off-by: Philip Withnall <withnall@endlessm.com>
| | * | docs: Use ‘Returns:’ instead of the invalid ‘@returns’Philip Withnall2018-08-131-8/+16
| | | | | | | | | | | | | | | | | | | | | | | | This is based on the commit 59a24ab5a3 in GLib. Signed-off-by: Philip Withnall <withnall@endlessm.com>
| | * | Update FSF’s addressPhilip Withnall2018-08-135-15/+5
| | | | | | | | | | | | | | | | | | | | | | | | (This is based on commit 892fc2e4 from dconf.) Signed-off-by: Philip Withnall <withnall@endlessm.com>
| | * | gio/gvdb/: LGPLv2+ -> LGPLv2.1+Sébastien Wilmet2018-08-135-5/+5
| | | | | | | | | | | | | | | | https://bugzilla.gnome.org/show_bug.cgi?id=776504
| | * | Avoid calling Standard C string/array functions with NULL argumentsPhilip Withnall2018-08-131-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | glibc string.h declares memcpy() with attribute(nonnull(1,2)), causing calls with NULL arguments to be treated as undefined behaviour. This is consistent with ISO C99 and C11, which state that passing 0 to string functions as an array length does not remove the requirement that the pointer to the array is a valid pointer. gcc -fsanitize=undefined catches this while running OSTree's test suite. Similarly, running the GLib test suite reports similar issues for qsort(), memmove(), memcmp(). (This is a partial cherry-pick of commit e5ed410c8c0fe823883 from GLib.) Signed-off-by: Simon McVittie <smcv@debian.org> Bug: https://bugzilla.gnome.org/show_bug.cgi?id=775510 Reviewed-by: Colin Walters
| | * | doap: Update maintainers list to synchronise with GLibPhilip Withnall2018-08-131-3/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | GVDB is essentially part of GLib, so should have the same maintainer list. At least this way, it’s not just maintained by one absentee maintainer. Signed-off-by: Philip Withnall <withnall@endlessm.com>
| | * | reader: embrace GBytesRyan Lortie2012-11-092-129/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Drop gvdb_table_new_from_data() and add gvdb_table_new_from_bytes(). Since the underlying backingstore of a GvdbTable is now always refcounted, drop the refcounting on GvdbTable itself.
| | * | gvdb-reader: drop gvdb_table_walk()Ryan Lortie2012-07-092-146/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The attempt at the simple method for preventing unbounded recursion proved to be insufficient due to the existence of dconf databases in the wild that violated the rule (leading to the entire content of the database being scrapped). It also still had the ugly assert for less than 64 levels of recursion that could have been hit by a determined advisary. gvdb_table_get_names() allows the dconf-service to do everything it needs without the troubles associated with the walk approach.
| | * | gvdb-reader.c: add gvdb_table_get_names()Ryan Lortie2012-07-092-1/+152
| | | | | | | | | | | | | | | | This function lists off all names that appear within a particular hash.
| | * | remove a stray variableRyan Lortie2012-07-081-2/+0
| | | | | | | | | | | | | | | | | | | | This was used to implement a much more complicated check which was dismissed in favour of the simple 'must follow in file' approach.
| | * | gvdb-reader: robustness improvementsRyan Lortie2012-07-061-13/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Improve the robustness of gvdb-reader in two ways. First: ensure that the result of gvdb_table_has_value() always agrees with gvdb_table_get_value(). Those two could disagree in the case that the value was recorded as existing but pointed to an out-of-bounds region. Second: prevent gvdb_table_walk() from getting stuck in finite loops due to self-referential directories.
| | * | more whitespace fixesRyan Lortie2012-07-051-5/+5
| | | |
| | * | gvdb-reader: refuse to open file with small headerRyan Lortie2012-07-051-26/+28
| | | | | | | | | | | | | | | | | | | | Clean up the logic for dealing with invalid headers and include the case where the file is too small to contain a fully-formed header.
| | * | gvdb-reader: correct whitespace damageRyan Lortie2012-07-051-33/+33
| | | |
| | * | builder: Note don't actually implement bloom filtersColin Walters2012-03-081-0/+7
| | | |
* | | | Merge branch '1488-o-cloexec-again' into 'master'Matthias Clasen2018-08-161-0/+18
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | gspawn: Use fcntl() to work around systems which don’t support O_CLOEXEC Closes #1488 See merge request GNOME/glib!242
| * | | | gspawn: Use fcntl() to work around systems which don’t support O_CLOEXECPhilip Withnall2018-08-111-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Somehow, we are still limping along with partial support for OS X <10.7. Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/1488
* | | | | Merge branch 'bindung-unbind-fix' into 'master'Philip Withnall2018-08-162-3/+86
|\ \ \ \ \ | |_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | g_binding_unbind: make it more introspection friendly; allow calling it multiple times. Fixes #1373 Closes #1373 See merge request GNOME/glib!244
| * | | | g_binding_unbind: make it more introspection friendly; allow calling it ↵Christoph Reiter2018-08-162-3/+86
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | multiple times. Fixes #1373 g_object_bind_property() (transfer none) returns a GBinding with an existing internal reference which is active as long as the "binding" is. This allows to optionally use the binding without any memory management, as it will remove itself when it is no longer needed. There are currently three ways to remove the "binding" and as a result the reference: 1) Either the source or target dies and we get notified by a weakref callback 2) The user unrefs the binding until it is destroyed (which is semi-legal, but worked and is used in the test suite) 3) The user calls g_binding_unbind() In case (3) the problem was that it always calls unref even if the "binding" is already gone, leading to crashes when called from bindings multiple times. In #1373 and !197 it was noticed that a function always unrefs which would be a "transfer full" annotation, but the problem here is that it should only remove the ref when removing the "binding" and the annotation should stay "transfer none". As a side effect of this fix it is now also possible to call g_binding_unbind() multiple times where every call after the first is a no-op. This also adds explicit tests for case (1) and (3) - only case (3) is affected by this change.
* | | | | Update German translationMario Blättermann2018-08-151-1284/+1240
|/ / / /
* | | | Merge branch 'fix-overlayfs-trashing-1027' into 'master'Ondrej Holy2018-08-133-33/+36
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | Fix trashing on overlayfs Closes #1027 See merge request GNOME/glib!182
| * | | Fix trashing on overlayfsIain Lane2018-08-132-6/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In order to determine whether to trash a file to the home directory, we compare its st_dev to our home directory's st_dev field. This is the wrong thing to do on overlayfs when deleting files, because st_dev contains the ID of the filesystem providing the file (which can be the lower or upper filesystem), but directories always return the ID of the overlayfs. Thus the comparison fails and we are unable to trash the file. Fix this by checking st_dev of the parent directory when we are deleting a file. Also adjust `test_trash_not_supported` for this - make its st_dev check look at the parent directory's `st_dev` rather than the temporary file's own. Fixes #1027.
| * | | Revert "glocalfile: Check that parent device is the same when trashing"Iain Lane2018-08-132-27/+7
|/ / / | | | | | | | | | This reverts commit 15cdcd2e0b4d18487dc71e3adc85e3bc8090058a.
* | | Fix indicative gschema.dtd regarding range.Arnaud B2018-08-131-2/+2
| | | | | | | | | The range can have only a "min" or only a "max" attribute, and can even have no attributes at all.
* | | Update French translationClaude Paroz2018-08-121-1343/+1332
| | |
* | | Merge branch '225-iso-8601-test-tz' into 'master'Emmanuele Bassi2018-08-121-1/+14
|\ \ \ | | | | | | | | | | | | | | | | tests: Explicitly set TZ=UTC for g_time_val_from_iso8601() testing See merge request GNOME/glib!243
| * | | tests: Explicitly set TZ=UTC for g_time_val_from_iso8601() testingPhilip Withnall2018-08-111-1/+14
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some of the test vectors don’t specify a timezone, so the local one is used; the comparisons to the expected results (which are in UTC) then fail. See discussion in https://gitlab.gnome.org/GNOME/glib/merge_requests/225. Signed-off-by: Philip Withnall <withnall@endlessm.com>
* | | Update Turkish translationEmin Tufan Çetin2018-08-121-1353/+1260
| | |
* | | Update Polish translationPiotr Drąg2018-08-121-1344/+1333
| | |
* | | Merge branch 'wjt/glib-mkenums-filename-basename-in-fhead-ftail' into 'master'Philip Withnall2018-08-112-90/+167
|\ \ \ | |/ / |/| | | | | | | | glib-mkenums: forbid @filename@/@basename@ in fhead and ftail See merge request GNOME/glib!241
| * | glib-mkenums: improve and correct argument documentationWill Thompson2018-08-101-6/+7
| | | | | | | | | | | | | | | | | | | | | ftail is not per-input-file, it is the footer for the entire output file. You cannot have fewer informations.
| * | glib-mkenums: don't support @filename@/@basename@ in fhead/ftailWill Thompson2018-08-102-20/+91
| | | | | | | | | | | | | | | | | | | | | As discussed in https://gitlab.gnome.org/GNOME/glib/merge_requests/135#note_253986 it doesn't really make sense to support these outside the templates for any particular header file. Leave them unsubstituted, with a warning.
| * | tests: mkenums: placate flake8Will Thompson2018-08-101-2/+2
| | |
| * | tests: refactor running glib-mkenumsWill Thompson2018-08-101-63/+68
| | | | | | | | | | | | | | | | | | | | | | | | | | | Part of runMkenumsWithHeader() was duplicated in test_reproducible(), and would otherwise need to be duplicated again in upcoming tests. Many places duplicated decoding stdout/stderr and checking the exit code. Introduce a named tuple for the returned fields; and factor out writing a template file to pass with --template.
* | | Merge branch 'ossfuzz-9815-time-signed-arithmetic' into 'master'Xavier Claessens2018-08-101-1/+1
|\ \ \ | |/ / |/| | | | | | | | gtimer: Ensure arithmetic is correctly signed for ISO 8601 parsing See merge request GNOME/glib!240
| * | gtimer: Ensure arithmetic is correctly signed for ISO 8601 parsingPhilip Withnall2018-08-101-1/+1
|/ / | | | | | | | | | | | | | | | | When calculating the value of a timezone offset, ensure that any offsets done with negative numbers are done in a signed integer. oss-fuzz#9815 Signed-off-by: Philip Withnall <withnall@endlessm.com>
* | Merge branch '1481-variant-parse-overflow' into 'master'Emmanuele Bassi2018-08-092-16/+44
|\ \ | | | | | | | | | | | | | | | | | | gvariant: Fix bounds checking in GVariant text format parser Closes #1481 See merge request GNOME/glib!236
| * | gvariant: Fix bounds checking in GVariant text format parserPhilip Withnall2018-08-092-16/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The token_stream_peek() functions were not doing any bounds checking, so could potentially read 1 byte off the end of the input blob. This was never noticed, since the input stream is almost always a nul-terminated string. However, g_variant_parse() does allow non-nul-terminated strings to be used with a @limit parameter, and the bugs become apparent under valgrind if that parameter is used. This includes modifications to the test cases to cover the non-nul-terminated case. Spotted by ossfuzz. Signed-off-by: Philip Withnall <withnall@endlessm.com>
View Lorry Controller Status