Debian Patches
Status for cjs/128.0-2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| upstream/modules-package-Fix-checking-interface-properties.patch | modules/package: Fix checking interface properties GObject.type_default_interface_ref() is no longer introspectable for some reason, but as it is deprecated in favor of GObject.type_default_interface_get() anyway, use that instead. |
=?utf-8?q?Florian_M=C3=BCllner?= <fmuellner@gnome.org> | no | 2025-09-12 | ||
| upstream/overrides-Gio-Enable-platform-specific-wrappers-only-on-n.patch | overrides/Gio: Enable platform-specific wrappers only on newer GLib | =?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | 2025-09-12 | ||
| upstream/overrides-Gio-Add-wrappers-for-platform-specific-Gio-func.patch | overrides/Gio: Add wrappers for platform-specific Gio functions GLib will not expose anymore platform specific functions in Gio namespace as it used to do when GI Repository 1.0 was used, in order to keep retro-compatibility in gjs applications, generate wrappers for Gio platform-specific definitions that we used to provide inside the main Gio object, but warn the users of these APIs that they should migrate to GioUnix or GioWin32 instead. |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | 2025-09-11 | ||
| upstream/Add-JS-API-wrapping-warn_deprecated_once_per_callsite.patch | Add JS API wrapping warn_deprecated_once_per_callsite Expose it in the print module |
Philip Chimento <philip.chimento@gmail.com> | no | 2025-09-12 | ||
| upstream/overrides-Gio-Use-print-s-warnDeprecatedOncePerCallsite-t.patch | overrides/Gio: Use print's warnDeprecatedOncePerCallsite to warn Re-use the C definition to warn when using a deprecated namespace instead of doing the same in pure JS. |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | 2025-09-12 | ||
| upstream/cjs-deprecation-Use-a-larger-deprecation-stack-for-JS-inv.patch | cjs/deprecation: Use a larger deprecation stack for JS invoked requests When using warnDeprecatedOncePerCallsite() from JS we need to use a larger stack to track the call site, otherwise we may end up considering the same call site for different actual callers. In fact when using this in Gio.js override the call site is always the same, but we care about where that function is being invoked from. |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | 2025-09-12 | ||
| upstream/overrides-Gio-Use-Platform-prefix-for-platform-only-symbo.patch | overrides/Gio: Use Platform prefix for platform-only symbols In previous versions of GLib, platform-specific symbols such as GUnixMountMonitor were mapped in the Gio namespace as Gio.UnixMountMonitor, while since commit 05656829 we create wrappers such as Gio.MountMonitor. This is not correct, and does not serve the initial purpose of providing a backward compatible wrapper. So, use the same logic that we had before: if the GType of a symbol starts with G{Unix,Win32} we use the platform specific name as prefix of the wrapper type, so that it will be Gio.{Unix,Win32}TypeName |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | 2025-09-12 | ||
| upstream/gi-function-Implement-name-property-for-functions.patch | gi/function: Implement name property for functions JS functions have a name properties by default, but we did not implement it for our function wrappers. Given that there's no a defined specification for it and that it can be used for debugging purposes, use it to store the original C function name. |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | 2025-09-12 | ||
| upstream/overrides-Gio-Use-Platform-prefix-for-platform-only-funct.patch | overrides/Gio: Use Platform prefix for platform-only functions In case a platform-only function is being mapped inside the Gio namespace and that has a platform-specific prefix, then we should use it inside the more generic Gio namespace. This is preserving the pre-girepository-2.0 behavior |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | 2025-09-12 |