Debian Patches

Status for glib2.0/2.86.0-6

Patch Description Author Forwarded Bugs Origin Last update
ghash-Fix-entry_is_big-for-CHERI-architecture.patch ghash: Fix entry_is_big for CHERI architecture
The entry_is_big function checks if an entry fits into a so-called
small entry, i.e. into a guint. This optimizes space for hash tables
on 64 bit system with hash tables containing 32 bit entries.

This code actually checks if the highest 32 bits are set, which would
become an issue with CHERI and its 128 bit pointers.		 Tobias Stoeckmann <tobias@stoeckmann.org> yes upstream upstream, 2.86.1, commit:cf97e674abf98fe41f7276400ea75809e27539c9 2025-08-25
ghash-Handle-all-table-sizes-in-iterator.patch ghash: Handle all table sizes in iterator
A table size of 2**31 cannot be represented in a gint. Adjust
RealIter to use a guint for its current position to support the largest
power of two possible for a hash table size.

This makes sure that g_hash_table_iter_next does not trigger a signed
integer overflow, which would eventually lead to an out of boundary
read.

With input by Philip Withnall.		 Tobias Stoeckmann <tobias@stoeckmann.org> yes upstream upstream, 2.86.1, commit:7367c518f1ed9f06e11c336e0fc28bfb1547a652 2025-08-25
ghash-Fix-signed-integer-overflow-in-g_hash_table_set_shi.patch ghash: Fix signed integer overflow in g_hash_table_set_shift
Shifting 1 by 31 bits triggers a signed integer overflow. Use 1u
for unsigned data type to allow such operation.		 Tobias Stoeckmann <tobias@stoeckmann.org> yes upstream upstream, 2.86.1, commit:f8bda4d10990a1e229fc3c3fd09b263ef6f99288 2025-08-25
gbookmarkfile-Escape-icon-href-and-mime.patch gbookmarkfile: Escape icon href and mime
If callers supply strings containing unescaped characters for icon href
or mime, then dumping the content can lead to corrupted files.		 Tobias Stoeckmann <tobias@stoeckmann.org> no upstream, 2.86.1, commit:f795a8a5de943ea764f120a874b202400086c3e4 2025-08-28
Update-Ukrainian-translation.patch Update Ukrainian translation Yuri Chornoivan <yurchor@ukr.net> no upstream, 2.86.1, commit:4310757baac41eab3987a00d01d2a9ebf8e9c25b 2025-09-05
Update-Catalan-translation.patch Update Catalan translation Jordi Mas <jmas@softcatala.org> no upstream, 2.86.1, commit:a04e18fc6d85e0b09f292054e5a87eef1e5cf1b6 2025-09-05
Update-Lithuanian-translation.patch Update Lithuanian translation =?utf-8?q?Aurimas_=C4=8Cernius?= <aurimas.cernius@mailo.com> no upstream, 2.86.1, commit:fcaefd2fa6ec3cda415f5b2c4893c461ad017c3d 2025-09-05
tests-Fix-clang-compilation-warnings.patch tests: Fix clang compilation warnings
With these adjustments, building with clang leads to no warnings:

- The "{ NULL }" statement could be replaced with "{ 0 }" to satisfy
clang, but this way it's explicitly filling all fields
- Even though "i" is not read with these g_array_binary_search calls,
it rightfully should be set		 Tobias Stoeckmann <tobias@stoeckmann.org> no upstream, 2.86.1, commit:c546ac20d8ec9fe7c52a2a8ebb256c9052710f57 2025-09-05
gmem-Replace-SIZE_OVERFLOWS-with-g_size_checked_mul.patch gmem: Replace SIZE_OVERFLOWS with g_size_checked_mul
Using the builtin multiplication checks leads to less instructions used
for these common functions (true for clang as well as gcc on x86_64).

Also, from a C perspective, the result is re-used, making code audits
easier.		 Tobias Stoeckmann <tobias@stoeckmann.org> no upstream, 2.86.1, commit:ceb5ac4925c0b7beecc9578942d9ecb2c76eb2bb 2025-09-05
Update-Brazilian-Portuguese-translation.patch Update Brazilian Portuguese translation Rafael Fontenelle <rffontenelle@gmail.com> no upstream, 2.86.1, commit:9e1241a0d017b0c3db4e5a0771b3ad4eb6d672ae 2025-09-05
Update-eu-translation.patch Update eu translation Asier Saratsua Garmendia <asier.sarasua@gmail.com> no upstream, 2.86.1, commit:1177c8eae3ee46bacdc030805dbfc3df3a158193 2025-09-06
Update-Korean-translation.patch Update Korean translation Changwoo Ryu <cwryu@debian.org> no upstream, 2.86.1, commit:89a20f8c5b9f09277481bca7766c113e2a829067 2025-09-06
Update-Japanese-translation.patch Update Japanese translation
From https://l10n.gnome.org/vertimus/glib/main/po/ja/		 Makoto Sakaguchi <ycco34vx@gmail.com> no upstream, 2.86.1, commit:5b450a2390bceb0f3fe625d8c8f8bd4495b665a1 2025-09-07
Update-Galician-translations.patch Update Galician translations Fran Dieguez <fran.dieguez@situm.com> no upstream, 2.86.1, commit:31c519a8518c674bd0303ecac7ee71292a480ab8 2025-09-08
Update-Hungarian-translation.patch Update Hungarian translation =?utf-8?b?QmFsw6F6cyDDmnI=?= no upstream, 2.86.1, commit:7a5a7a7133c30de868594698f919c4c638c9c6fe 2025-09-09
gstrfuncs-Check-string-length-in-g_strescape.patch gstrfuncs: Check string length in g_strescape
If the input string is too large on a 32 bit system, it is possible
to trigger an integer overflow which subsequently leads to an out of
boundary write.		 Tobias Stoeckmann <tobias@stoeckmann.org> no upstream, 2.86.1, commit:b274f829638282a71757620ad226869d9cc4f7df 2025-09-09
gio-tests-socket-listener-should-depend-on-libdl.patch `gio/tests/socket-listener` should depend on `libdl` Uwe Korn <gnome@uwekorn.com> yes upstream upstream, 2.86.1, commit:2b0f5304bdf8804855ca3831d9ac265038442c20 2025-09-11
gutils-Support-test-env-in-load_user_special_dirs.patch gutils: Support test env in load_user_special_dirs
XDG_CONFIG_DIR and HOME can be overridden with test environments. Read
these variables before building them again.

It's not possible to call the getter functions directly because the
caller of load_user_special_dirs already holds a lock and locking again
is undefined behavior and could lead to deadlocks.

Separate the functionality out into unlocked functions which definitely
have to be static to not expose them. Use them while holding the lock.		 Tobias Stoeckmann <tobias@stoeckmann.org> no upstream, 2.86.1, commit:82c83a88712fb6e8ff16e228a6806137058b508b 2025-09-12
Update-Turkish-translation.patch Update Turkish translation
Approved by Emin Tufan Çetin
https://l10n.gnome.org/vertimus/glib/main/po/tr/		 =?utf-8?q?Sabri_=C3=9Cnal?= <yakushabb@gmail.com> no upstream, 2.86.1, commit:25b5bf8ea7faeae2da0910b7791a50926b74fd71 2025-09-14
gutils-Only-allow-HOME-in-load_user_special_dirs.patch gutils: Only allow $HOME in load_user_special_dirs
Make sure that the allowed environment variable is actually HOME, not
any environment variable starting with HOME, e.g. HOMER.		 Tobias Stoeckmann <tobias@stoeckmann.org> no upstream, 2.86.1, commit:2e88bd5fdd76da70571f06ae47246ea13dd64095 2025-09-11
gutils-Strip-all-trailing-slahes-in-load_user_special_dir.patch gutils: Strip all trailing slahes in load_user_special_dirs
Do what the comment states and strip all trailing slashes. Also, do not
strip the trailing slash if it's the only character left, i.e. if it
denotes the root directory.		 Tobias Stoeckmann <tobias@stoeckmann.org> no upstream, 2.86.1, commit:43d9e506548a4a00446fa365eb0871d942cb19d0 2025-09-11
gutils-Reject-unquoted-entries-in-load_user_special_dirs.patch gutils: Reject unquoted entries in load_user_special_dirs
If the end quote is missing, reject the entry. Please note that this
still allows entries with an uneven amount of quotes, e.g. "/"".		 Tobias Stoeckmann <tobias@stoeckmann.org> no upstream, 2.86.1, commit:9a2d221e90b5e00062e32b610754a98cc25ed834 2025-09-11
gutils-Handle-huge-lines-in-load_user_special_dirs.patch gutils: Handle huge lines in load_user_special_dirs
If a line is longer than G_INTMAX, still treat it correctly without
possibly provoking an out of boundary read.		 Tobias Stoeckmann <tobias@stoeckmann.org> no upstream, 2.86.1, commit:300722b6c42639891bc37cab0de0e03fb2a9e127 2025-09-11
fuzzing-add-special-dirs-fuzzing-test.patch fuzzing: add special dirs fuzzing test
Split custom user-dirs.dirs parser into its own gutilsprivate.c file
for easier fuzzing support and add a fuzzing test.		 Tobias Stoeckmann <tobias@stoeckmann.org> no upstream, 2.86.1, commit:ed594d819e94ad2f399c9167bfe37f728e1b6544 2025-09-15
fuzzing-Fix-fuzz_special_dirs.patch fuzzing: Fix fuzz_special_dirs
Always NUL-terminate the data, which g_file_get_contents does as well.
This fixes unnecessary fuzzer warnings.

For further clarification of this requirement, rename the internally
used function.		 Tobias Stoeckmann <tobias@stoeckmann.org> yes upstream upstream, 2.86.1, commit:0bebad35cf212c759cf6859d171d0655b0d87310 2025-09-16
get_help-Ignore-width-of-invisible-options.patch get_help(): Ignore width of invisible options
When get_help() gets ready to lay out the help text into columns,
it first goes through and computes the max_width of the strings in
the left column. Problem is, it measures the width of every
available option, whether or not they'll actually be displayed.

Instead, let's use the same criteria used when deciding whether
to display an option, to decide whether or not to account for it
when computing max_width. This way, the layout is sized for the
help that's actually being produced.		 "FeRD (Frank Dana)" <ferdnyc@gmail.com> yes upstream upstream, 2.86.1, commit:bff4dcb3d803c73c6601d75fe2d700ee7016af03 2025-09-12
gutils-Handle-singletons-in-unlocked-functions.patch gutils: Handle singletons in unlocked functions
Make sure that results of build functions are stored in singletons to
avoid creating multiple instances which eventually could leak.

(cherry picked from commit 18a7e7b4a2f248d3c70b3f50a56e16003d625d36)		 Michael Catanzaro <mcatanzaro@redhat.com> yes upstream upstream, 2.86.1, commit:bcf4274f4381841f90b7b2ea898190d6fa31e4a5 2025-09-16
Update-Esperanto-translation.patch Update Esperanto translation Kristjan ESPERANTO <kristjan.schmidt@googlemail.com> no upstream, 2.86.1, commit:dacbf04a008b2eeceab88c95223944e9f46d743c 2025-09-16
Update-Serbian-translation.patch Update Serbian translation =?utf-8?b?0JzQuNC70L7RiCDQn9C+0L/QvtCy0LjRmw==?= <gpopac@gmail.com> no upstream, 2.86.1, commit:95f85b7e44c6d689e4bb29b6ad6d351572f645cc 2025-09-16
gio-tests-Factor-out-connection_wait_for_bus-from-gdbus-s.patch gio/tests: Factor out connection_wait_for_bus() from gdbus-subscribe Simon McVittie <smcv@debian.org> no 2025-09-19
gio-tests-Avoid-a-race-condition.patch gio/tests: Avoid a race condition
We have two things happening in parallel:

1. The GDBus worker thread writes out an AddMatch call to the socket,
the message bus reads that method call from the other end of the
socket, and the message bus responds by adding the match rule
for the signal subscription

2. The main thread forks, and the child execs
gdbus-connection-flush-helper, which sends the signal that we are
expecting; the message bus receives that signal, and broadcasts it
to subscribers, if any

Normally (1.) wins the race because exec'ing a child process is more
time-consuming than IPC, and the test passes.

However, it is possible for (2.) to win the race. If so, we will never
receive the expected signal (because it was received by the message bus
before the AddMatch() method call, so at the time it was received, the
test was not yet a subscriber); the test waits until the timeout and
then gives up, and the test fails.

For whatever reason, Debian's s390x buildd seems to be reliably failing
this test since this week, having previously passed. I don't know what
changed. I can (very rarely) reproduce the race condition described
above on a developer-accessible s390x machine by repeatedly running the
/gdbus/connection/flush test in a loop.		 Simon McVittie <smcv@debian.org> no debian 2025-09-19
gio-tests-Convert-the-time-to-wait-for-expected-signal-in.patch gio/tests: Convert the time to wait for expected signal into a constant

No functional change.		 Simon McVittie <smcv@debian.org> no 2025-09-19
gio-tests-Wait-up-to-10-seconds-for-a-signal-to-be-receiv.patch gio/tests: Wait up to 10 seconds for a signal to be received
If the build/test machine is slow, heavily-loaded or otherwise
inconvenienced, it might take a few seconds for the signal to be sent
by the subprocess, received by the message bus, re-broadcasted by the
message bus and received by the test code. Wait a few more seconds
before giving up.

If this test is successful, increasing this timeout will not slow it
only make any difference if the test would have failed.		 Simon McVittie <smcv@debian.org> no 2025-09-19
ghostutils-Treat-0x80-and-above-as-non-ASCII.patch ghostutils: Treat 0x80 (and above) as non-ASCII
Any ASCII character above 0x7F should be treated as UTF-8 in
ghostutils functions because GLib expects host names to be either
punycode encoded or in valid UTF-8 format.

The checks in gutf8.c already treat 0x80 as non-ASCII, but two checks
in ghostutils.c erroneously check for "great than" not "greater than or
equal to".

Clarify this by adding a new macro which is reused by PUNICODE_IS_BASIC
for better documentation in code.		 Tobias Stoeckmann <tobias@stoeckmann.org> no upstream, 2.86.1, commit:e56606de3dbc510e9f7c9a75b66927968dbb51b8 2025-09-21
gutils-Mark-load_user_special_dirs-unlocked.patch gutils: Mark load_user_special_dirs unlocked
The load_user_special_dirs function performs no internal locking, which
means that callers must already hold the g_utils_global lock. Since we
mark some getters as unlocked by now, do the same with
load_user_special_dirs to highlight this additional requirement.

Suggested by Michael Catanzaro		 Tobias Stoeckmann <tobias@stoeckmann.org> no upstream, 2.86.1, commit:3d7caa9407d5627b00e76f6511cdfa3cd058476c 2025-09-16
gutils-Fix-file-name-in-comment.patch gutils: Fix file name in comment
The implementation can be found in gosxutils.m.		 Tobias Stoeckmann <tobias@stoeckmann.org> no upstream, 2.86.1, commit:d30730bc71eba9570cca877a266efe1f4ef58938 2025-09-16
tests-Use-G_TEST_OPTION_ISOLATE_DIRS-for-utils-tests.patch tests: Use G_TEST_OPTION_ISOLATE_DIRS for utils tests
Another test isolated.

This does mean moving one of the test cases from the suite out into a
separate suite, as it explicitly relies on running without
`G_TEST_OPTION_ISOLATE_DIRS`, and I think that makes sense. The other
test cases run fine when isolated.		 Philip Withnall <pwithnall@gnome.org> no upstream, 2.86.1, commit:133aed18752f0d7af761a38f39f8dbb7ba90c967 2025-09-19
tests-Move-user-special-dirs-test-from-utils-isolated.c-t.patch tests: Move user-special-dirs test from utils-isolated.c to utils.c
`utils-isolated.c` is meant for testing the behaviour of
`G_TEST_OPTION_ISOLATE_DIRS`, not testing the general behaviour of
`gutils.c`. My mistake for not noticing this at code review time when
the test was added.

This introduces no functional changes, just moves a test around.		 Philip Withnall <pwithnall@gnome.org> no upstream, 2.86.1, commit:66aee5e2c85d617c4632fc157ff7a93381f997dc 2025-09-18
tests-Rename-a-couple-of-tests-for-consistency.patch tests: Rename a couple of tests for consistency Philip Withnall <pwithnall@gnome.org> no upstream, 2.86.1, commit:0a0da8b21a407f39e9d2e32c30e38bcd0e177947 2025-09-18
tests-Fix-a-minor-leak-in-the-utils-test.patch tests: Fix a minor leak in the utils test
Found with `meson test --setup valgrind`, although I also had to change
relevant lines in `glib/tests/meson.build` temporarily to avoid the
other tests in the file taking forever:
```
'utils' : {
'c_standards': c_standards.keys(),
'args': ['-p', '/utils/user-special-dirs'],
},
```		 Philip Withnall <pwithnall@gnome.org> no upstream, 2.86.1, commit:888415030e752b86a6a92e7628a83f0e0764b692 2025-09-18
gutils-Fix-a-leak-when-user-dirs.dirs-declares-a-variable.patch gutils: Fix a leak when user-dirs.dirs declares a variable twice
Found by the oss-fuzz test for this parser,
`fuzzing/fuzz_special_dirs.c`.


oss-fuzz#445870121
oss-fuzz#445848222		 Philip Withnall <pwithnall@gnome.org> no upstream, 2.86.1, commit:e4c2b08218705f3aa12ed1be4ddea3371ce2f39c 2025-09-18
gutils-Fix-deliberate-leak-code-in-g_reload_user_special_.patch gutils: Fix deliberate-leak code in g_reload_user_special_dirs_cache()

It seems it wasn’t behaving as advertised: it was freeing all the old
string values unless they were strcmp-equal to the new ones, in which
case the new ones were discarded.

What’s actually documented is that the old values are always leaked,
unless they’re strcmp-equal to the new ones.

Adjust the code to match the documentation. A unit test will be added in
a following commit.		 Philip Withnall <pwithnall@gnome.org> no upstream, 2.86.1, commit:ab09a3e933cb15572a101c7b7cf30e7810342130 2025-09-19
gutils-Move-the-special-case-default-value-for-G_USER_DIR.patch gutils: Move the special case default value for G_USER_DIRECTORY_DESKTOP

Otherwise it isn’t set on every code path, and it’s possible for a
caller to receive `NULL` when they call `g_get_user_special_dir
(G_USER_DIRECTORY_DESKTOP)`, i.e. after calling
`g_reload_user_special_dirs_cache()`.		 Philip Withnall <pwithnall@gnome.org> no upstream, 2.86.1, commit:964c3f10699f000dba996ce13d04de7f28b63e41 2025-09-19
tests-Factor-out-a-helper-function-in-the-utils-tests.patch tests: Factor out a helper function in the utils tests
This introduces no functional changes, it just factors out a helper to
set a mock `user-dirs.dirs` file, so that we can do the same in multiple
tests.

It does add a little more error checking to the helper code though; in
particular it checks that the test is running with
`G_TEST_OPTION_ISOLATE_DIRS`.		 Philip Withnall <pwithnall@gnome.org> no upstream, 2.86.1, commit:fa1ed222e2a91f7eca0171ff04f87070af7f1086 2025-09-19
tests-Add-a-test-for-g_reload_user_special_dirs_cache.patch tests: Add a test for g_reload_user_special_dirs_cache()
This test specifically checks whether the documented behaviour of
deliberately leaking old special dirs strings (which might still be
pointed to in user code) works.

I haven’t gone back and used this new unit test with an older version of
GLib, but I suspect the ‘deliberate leak’ code hasn’t worked for a
while. See the changes in the previous few commits, which were necessary
to get this unit test to pass.

The previous `test_user_special_dirs()` test has been deleted, as what
it was testing has been entirely subsumed into the new test.		 Philip Withnall <pwithnall@gnome.org> no upstream, 2.86.1, commit:25dd814ed8e11cea7b509cacd04fb49459f3ef13 2025-09-19
Update-Portuguese-translation.patch Update Portuguese translation Hugo Carvalho <hugokarvalho@hotmail.com> no upstream, 2.86.1, commit:500f836370552dffb95926eead4dec0a3d4f5ff9 2025-09-24
Update-Romanian-translation.patch Update Romanian translation Antonio Marin <gnmer.6qxyg@slmail.me> no upstream, 2.86.1, commit:6fa4379cdbec8fd7bba21570f25b9360484cdd8a 2025-09-27
girnode-Fix-computation-of-union-member-offsets.patch girnode: Fix computation of union member offsets
Regression from 501ff95c. Union member offsets are always 0, but we need
to mark them as 'COMPUTED' otherwise they are not written to the
typelib, which results in gi_field_info_get_offset() returning 0xffff.

Since gi_field_info_get/set_field() cannot check that the offset is
within the size of the struct or union, that means poking into invalid
memory addresses.

This also adds some basic tests for GIFieldInfo which would have caught
this bug.		 Philip Chimento <philip.chimento@gmail.com> yes upstream upstream, 2.86.1, commit:ecbf92a58687d82de42e942eeb81c92835047f6d 2025-09-29
Update-British-English-translation.patch Update British English translation Bruce Cowan <bruce@bcowan.me.uk> no upstream, 2.86.1, commit:0574833f42cb5c8e607bb6d45ca55c9e1a6b78ec 2025-10-02
gtype-Define-copy-and-free-functions-for-GTypeClass-and-G.patch gtype: Define copy and free functions for GTypeClass and GTypeInterface

We have some (deprecated) methods that technically still return
transfer-full instances of GTypeClass's and GTypeInterface's.

The introspection scanner cannot generate bindings for them though since
it does not know how to manage their lifecycle, and we end up skipping
these symbols.

This is breaking some language bindings, and in particular gjs [1] and
lua-lgi, that were using the .ref methods.

While we should not use deprecated functions in the language bindings,
these symbols should still be introspected.

[1] https://gitlab.gnome.org/GNOME/gjs/-/issues/711		 =?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> yes 2025-09-10
01_gettext-desktopfiles.patch Call gettext if .desktop file does not have inline translations
Patch from OpenSUSE via Ubuntu, original author unknown. Martin Pitt and
Vincent Untz appear to be the main authors.

Reworked slightly by Philip Withnall to avoid exposing new public API
for the non-standard keys.		 Philip Withnall <withnall@endlessm.com> yes upstream 2017-11-23
debian/02_gettext-desktopfiles-ubuntu.patch Provide backwards compatibility for 01_gettext-desktopfiles.patch for X-{Debian,Ubuntu}-Gettext-Domain

Ubuntu-specific. 01_gettext-desktopfiles.patch was changed to use
X-GNOME-, so this is necessary until all our .desktop files are converted.		 Martin Pitt <mpitt@debian.org> no 2009-02-24
debian/03_disble_glib_compile_schemas_warning.patch Disable confusing (to users) warning about deprecated schema paths
Disable a warning when compiling schemas which are installed
into 'deprecated' locations. Users see this very often due to
glib-compile-schemas being called from libglib2.0-0's trigger and it is
not very useful for them.		 Iain Lane <iain.lane@canonical.com> not-needed 2012-09-10
debian/gdesktopappinfo-Try-using-x-terminal-emulator-for-Termina.patch gdesktopappinfo: Try using x-terminal-emulator for Terminal=true apps

Debian Policy provides x-terminal-emulator as an interface for launching
a preferred terminal, for some definition of "preferred". However, the
x-terminal-emulator alternative is a system-wide choice, so in situations
where for example a GNOME user and a KDE user share a computer, only one
of them can have the terminal that will match their desktop environment's
appearance and behaviour conventions as the x-terminal-emulator.

As a result, we still try to use a GTK-based terminal as a higher
preference than x-terminal-emulator. This is done on the assumption
that when apps are launched using GLib interfaces, they are most likely
to have been launched from a GTK application or GTK-based desktop
environment, and therefore a GTK-based terminal will be the best fit for
the desktop environment's conventions and appearance.

I've somewhat arbitrarily sorted x-terminal-emulator as less preferred
than KDE's Konsole, but more preferred than rxvt and various xterm
variants which are not associated with a particular desktop environment.		 Simon McVittie <smcv@debian.org> not-needed debian 2023-02-04
workarounds/timer-test-use-volatile-for-locals.patch timer test: use 'volatile' for locals
GCC seems to be failing to follow the letter of the C spec by allowing extra
precision in floating point values to persist across assignments which are
optimised away.

Force its hand by using 'volatile' on the locals in question.		 Ryan Lortie <desrt@desrt.ca> yes upstream 2014-03-04
workarounds/gwakeuptest-Be-less-parallel-unless-invoked-with-m-slow.patch gwakeuptest: Be less parallel unless invoked with -m slow
This is a workaround for test failures on the reproducible-builds
infrastructure, where a multi-threaded stress-test sometimes takes longer
to finish on x86_64 than it would have done on slow architectures like
arm and mips on the official Debian autobuilders. It is not clear why.

This change will make this test more likely to pass, but less likely to
detect bugs.		 Simon McVittie <smcv@debian.org> no debian 2017-12-18
workarounds/closures-test-Skip-on-arm-unless-flaky-tests-are-allowed.patch closures test: Skip on arm* unless flaky tests are allowed
Choosing the right number of iterations to avoid either taking literally
hours on some hardware, or getting spurious failures when one thread
starves another, seems to be too hard to get right in practice.
Make this test opt-in so that its failures aren't release-critical.
We can run it as a separate autopkgtest that is marked flaky.		 Simon McVittie <smcv@debian.org> not-needed debian 2019-01-03
workarounds/Disable-some-tests-on-slow-architectures-which-keep-faili.patch Disable some tests on slow architectures which keep failing the tests

[smcv: Modified to use g_test_skip() instead of omitting those test cases
completely, and allow them to be re-enabled with a Debian-specific
environment variable]		 Martin Pitt <martin.pitt@ubuntu.com> no 2012-09-27
workarounds/Skip-test-which-performs-some-unreliable-floating-point-c.patch Skip test which performs some unreliable floating point comparisons
[smcv: Modified to use g_test_skip() instead of omitting those test cases
completely, and allow them to be re-enabled with a Debian-specific
environment variable]		 Iain Lane <laney@debian.org> no upstream 2014-03-18
workarounds/Skip-unreliable-gdbus-threading-tests--by-default.patch Skip unreliable gdbus-threading tests by default
test_threaded_singleton() test to reproduce a race condition between
last-unref of the global singleton GDBusConnection and g_bus_get_sync().

test_method_calls_in_thread() checks that multiple threads can all make
method calls to the same proxy.

However, test setup intermittently times out with:

# GLib-GIO-DEBUG: run 0: refcount is 2, sleeping
Bail out! GLib-GIO-FATAL-ERROR: connection had too many refs

The current theory upstream is that this might be a reference leak in
test_delivery_in_thread().

Furthermore, test teardown is now often failing when destroying the test
bus.

Demote these tests to be run as part of the "flaky" autopkgtests, but
not at build time or in the part of the autopkgtest run that gates
progress into testing.		 Simon McVittie <smcv@debian.org> no upstream 2019-01-04
workarounds/gvariant-test-Don-t-run-at-build-time-on-mips.patch gvariant test: Don't run at build-time on mips
DEB_ALLOW_FLAKY_TESTS is not quite right here, because we don't know
that the test would fail if left for long enough - the problem is that
it doesn't get there, because generating random floating-point numbers
is very slow on some of our mips hardware. However, it has the right
practical effect.		 Simon McVittie <smcv@debian.org> no upstream 2019-07-26
workarounds/gdbus-server-auth-Normally-skip-flaky-DBUS_COOKIE_SHA1-te.patch gdbus-server-auth: Normally skip flaky DBUS_COOKIE_SHA1 tests
These intermittently fail on the buildds, but the failure cannot be
reproduced in a debugging environment.

We do not expect to use D-Bus over TCP on non-Windows platforms: we use
an AF_UNIX socket, which is much more robust and secure. However, when
using AF_UNIX, DBUS_COOKIE_SHA1 is unnecessary, because we can use the
more reliable EXTERNAL authentication.		 Simon McVittie <smcv@debian.org> not-needed 2020-11-19
workarounds/Skip-memory-monitor-dbus-test-if-not-specifically-request.patch Skip memory-monitor-dbus test if not specifically requested
This seems to be unreliable, particularly on non-x86.		 Simon McVittie <smcv@debian.org> no debian 2021-10-24
workarounds/tests-Skip-debugcontroller-test.patch tests: Skip debugcontroller test
This is known to be flaky upstream.		 Simon McVittie <smcv@debian.org> not-needed 2022-02-15
workarounds/testfilemonitor-Skip-if-we-are-avoiding-flaky-tests.patch testfilemonitor: Skip if we are avoiding flaky tests
See https://gitlab.gnome.org/GNOME/glib/issues/1634		 Simon McVittie <smcv@debian.org> no 2020-02-25
debian/girepository-Describe-the-Debian-specific-cross-prefixed-.patch girepository: Describe the Debian-specific cross-prefixed names Simon McVittie <smcv@debian.org> not-needed 2024-02-28

All known versions for source package 'glib2.0'

Links