4cad66580b
This partially reverts ed8e86a7d4. The change to add the criticals (commit ed8e86a7d4) is correct, but landed too late in the cycle. Let’s downgrade the criticals to debugs for now, to stop applications seeing a lot of new criticals in their output. Those criticals are particularly disruptive for command line applications and unit tests. Early in the next cycle, the debugs will be re-upgraded to criticals. This will give applications a whole additional cycle to fix their ambiguous use of API. It turned out that a lot of applications have latent bugs around calling `g_file_info_get_*()` without checking whether an attribute is set first, and were hence relying on the ‘unknown’ return value also being an appropriate default for them. This was compounded by the fact that several non-local GVFS backends were not setting `GFileInfo` attributes all the time, which caused the ‘missing attribute’ code path to be hit more frequently. For example, they would only call `g_file_info_set_is_hidden()` with a true value and never bother with a false one. It was further compounded by the fact that, while this change landed for the 2.75.4 release, there did not seem to be extensive integration testing of that release, and distributions and downstreams went straight to 2.76.0. That meant we missed the window between 2.75.4 and 2.76.0 to change, fix or revert this behaviour. GLib relies on distros and downstreams doing integration testing of unstable releases. We test with downstream GNOME as part of gnome-build-meta, but do not have the resources to do integration testing for everybody. Signed-off-by: Philip Withnall <pwithnall@endlessos.org> See: #2907 See: #2932 See: #2934 See: #2945 See: #2948
GLib
GLib is the low-level core library that forms the basis for projects such as GTK and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system.
The official download locations are: https://download.gnome.org/sources/glib
The official web site is: https://www.gtk.org/
Installation
See the file 'INSTALL.md'
Supported versions
Only the most recent unstable and stable release series are supported. All older versions are not supported upstream and may contain bugs, some of which may be exploitable security vulnerabilities.
See SECURITY.md for more details.
Documentation
API documentation is available online for GLib for the:
Discussion
If you have a question about how to use GLib, seek help on GNOME’s Discourse
instance. Alternatively, ask a question
on StackOverflow and tag it glib.
Reporting bugs
Bugs should be reported to the GNOME issue tracking system. You will need to create an account for yourself. You may also submit bugs by e-mail (without an account) by e-mailing incoming+gnome-glib-658-issue-@gitlab.gnome.org, but this will give you a degraded experience.
Bugs are for reporting problems in GLib itself, not for asking questions about how to use it. To ask questions, use one of our discussion forums.
In bug reports please include:
- Information about your system. For instance:
- What operating system and version
- For Linux, what version of the C library
- And anything else you think is relevant.
- How to reproduce the bug.
- If you can reproduce it with one of the test programs that are built
in the
tests/subdirectory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded.
- If you can reproduce it with one of the test programs that are built
in the
- If the bug was a crash, the exact text that was printed out when the crash occurred.
- Further information such as stack traces may be useful, but is not necessary.
Contributing to GLib
Please follow the contribution guide to know how to start contributing to GLib.
Patches should be submitted as merge requests to gitlab.gnome.org. If the patch fixes an existing issue, please refer to the issue in your commit message with the following notation (for issue 123):
Closes: #123
Otherwise, create a new merge request that introduces the change. Filing a separate issue is not required.
Default branch renamed to main
The default development branch of GLib has been renamed to main. To update
your local checkout, use:
git checkout master
git branch -m master main
git fetch
git branch --unset-upstream
git branch -u origin/main
git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main