commit 9389c5e747cc66361f0e1dd03b2c11fb5fff9c48
Author: Simon McVittie <smcv@debian.org>
Date: Sat Oct 18 15:48:44 2025 +0100
Update changelog
commit 073c11ab6550a4367e61c921e14ab4862c16d2ad
Merge: 40693740 444926af
Author: Simon McVittie <smcv@debian.org>
Date: Sat Oct 18 15:47:52 2025 +0100
Merge tag 'debian/3.50.2-1' into debian/latest
pygobject release 3.50.2-1 for unstable (sid)
commit 444926af16c36a073ce136057704fce703c3a466
Author: Simon McVittie <smcv@debian.org>
Date: Sat Oct 18 14:55:50 2025 +0100
Release to unstable
commit 4aa50ee23a12c1fe2e96393978eae51ce1448cde
Author: Simon McVittie <smcv@debian.org>
Date: Sat Oct 18 14:52:59 2025 +0100
Update changelog
commit 2a1fe70bd0dfd0ba325e742501bd548dbbcf008e
Author: Simon McVittie <smcv@debian.org>
Date: Sat Oct 18 14:44:25 2025 +0100
d/patches: Drop most patches, applied upstream
commit 5062a6dd1fe1617168a9b76723efa3ed5cf2a5b2
Author: Simon McVittie <smcv@debian.org>
Date: Sat Oct 18 14:43:18 2025 +0100
New upstream release
commit 75734a4e5cf76f96addea1e852fbeb8cc120dedb
Merge: 3dee4eb9 09fe0592
Author: Simon McVittie <smcv@debian.org>
Date: Sat Oct 18 14:43:18 2025 +0100
Update upstream source from tag 'upstream/3.50.2'
Update to upstream version '3.50.2'
with Debian dir 0f121fe6a27091e7e32128b781705ac536f1e3cd
commit 09fe0592e3cb10427397c28785455befe16a8992
Merge: ebbbcbb4 ad3de74e
Author: Simon McVittie <smcv@debian.org>
Date: Sat Oct 18 14:43:14 2025 +0100
New upstream version 3.50.2
commit ad3de74ee96f21102475297779a44965d3333a06
Author: Arjan Molenaar <gaphor@gmail.com>
Date: Sat Oct 18 13:25:31 2025 +0200
Update news for 3.50.2
commit b205fa004ebfda89c87e644c309af69525c151a6
Author: Arjan Molenaar <gaphor@gmail.com>
Date: Mon Feb 10 16:45:04 2025 +0100
Revert "override connection.register_object to prevent an invocation object from leaking"
This reverts commit bf80d0f34af5062fd1201d71fbcd3a34bf1d1a80.
It's causing issues with Anaconda (Fedora/RHEL installer).
See https://gitlab.gnome.org/GNOME/pygobject/-/issues/658
Leave test case in place, but make it "xfail".
commit 46fee99aa6dd7cbb75223ff918231c2d4a3e77cd
Author: Simon McVittie <smcv@debian.org>
Date: Wed Oct 23 12:01:24 2024 +0100
async: Use correct T_BOOL type for _asyncio_future_blocking
Declaring a PyMemberDef with type T_BOOL requires the corresponding C
type to be char, with value 0 or 1: when the member is read, CPython
will effectively be dereferencing
`* (char *) &pygiasync._asyncio_future_blocking`.
On little-endian architectures, in practice this worked, because the
low-order bits of an int are in the first byte, which would take value
0 or 1 as desired, with all other bits zero. However, on big-endian
architectures, the low-order bits of an int are in the last byte, so
reading the _asyncio_future_blocking attribute from Python code would
in practice always produce 0, even when the int field had been set to 1
from C code.
Reference: https://docs.python.org/3/c-api/structures.html#member-types
Resolves: https://gitlab.gnome.org/GNOME/pygobject/-/issues/650
Bug-Debian: https://bugs.debian.org/1085891
Signed-off-by: Simon McVittie <smcv@debian.org>
commit 3dee4eb9297382c6a7494abd197343bcb4f98ae1
Author: Simon McVittie <smcv@debian.org>
Date: Sat Oct 18 11:01:16 2025 +0100
New upstream release
commit 69fdde7329315e4029eba35c3b16d575f752b957
Merge: 862a0aec ebbbcbb4
Author: Simon McVittie <smcv@debian.org>
Date: Sat Oct 18 11:01:16 2025 +0100
Update upstream source from tag 'upstream/3.50.1'
Update to upstream version '3.50.1'
with Debian dir 458ce2765985e4e0ee183fd67727a5997fe9d109
commit ebbbcbb4a8ebd2d31c8391833cf5c2b803e6994e
Merge: 444a9b54 f40a6140
Author: Simon McVittie <smcv@debian.org>
Date: Sat Oct 18 11:01:11 2025 +0100
New upstream version 3.50.1
commit 862a0aec9f7b79ab97c0d4e70dfc7ec70718a069
Author: Simon McVittie <smcv@debian.org>
Date: Sat Oct 18 11:00:54 2025 +0100
d/watch: Only watch for 3.50.x on this branch
commit c73e402d92a3e5fbacfcd5427bcf91570c4b2158
Author: Simon McVittie <smcv@debian.org>
Date: Sat Oct 18 10:59:15 2025 +0100
d/watch: Convert to v5 format
commit f7512ff8ab9f01f528152d9549cf57bdda937cc6
Author: Simon McVittie <smcv@debian.org>
Date: Mon Oct 13 13:38:08 2025 +0100
Update changelog
commit 3ee6a720f71c473c4114f23c565784bcb94a9b47
Author: Simon McVittie <smcv@debian.org>
Date: Fri Oct 17 18:25:44 2025 +0100
d/copyright: Don't quote the FSF's former postal address here
commit 3c603c0a8d3e5fc8622ef91f78ada421650a2ef2
Author: Simon McVittie <smcv@debian.org>
Date: Mon Oct 13 13:47:20 2025 +0100
d/patches: Mark a patch as applied in 3.52.0
Gbp-Dch: ignore
commit 3cc71efb39f3def0fdd2dcb30c3ed2c7943a75a8
Author: Simon McVittie <smcv@debian.org>
Date: Mon Oct 13 13:21:00 2025 +0100
d/patches: Add patches from upstream 3.54.0 fixing some of the test failures with Python 3.14
Helps: #1117897
commit c0ffc3b7a0b77ea5bff591152a9c10d74b4a607a
Author: Simon McVittie <smcv@debian.org>
Date: Mon Oct 13 13:07:16 2025 +0100
d/patches: Replace GLib 2.86 compatibility patches with upstream's backport
commit 3319eea8b9dc04c808533089b8325b5ff84690c1
Author: Arjan Molenaar <gaphor@gmail.com>
Date: Sun Oct 12 17:18:12 2025 +0200
Add pre-commit config
This makes it easier to switch from branches.
Only Flake8 is included, since that's the only tool we run in the
pipeline.
commit 9ecd338fb02bfb1022cf4bee60cdb236ca159e0b
Author: Simon McVittie <smcv@debian.org>
Date: Wed Oct 8 11:04:20 2025 +0100
tests: Test GioUnix compatibility on all GLib versions back to 2.80
On older GLib versions we don't expect the classes and functions in
GioUnix to be aliases for their equivalents in Gio (as far as pygobject
can tell, they are distinct!) and we don't expect them to raise
deprecation warnings, but we can still test that they are functionally
usable.
Reproduces: https://gitlab.gnome.org/GNOME/pygobject/-/issues/719
Signed-off-by: Simon McVittie <smcv@debian.org>
commit 0a370b59b0fc06d002c067c14f12aa81eee4b1f3
Author: Simon McVittie <smcv@debian.org>
Date: Wed Oct 8 11:58:12 2025 +0100
overrides: Make GioUnix work as intended with older GLib
Resolves: https://gitlab.gnome.org/GNOME/pygobject/-/issues/719
Signed-off-by: Simon McVittie <smcv@debian.org>
commit 7de1e866f35b583e9dc6f8c865d8bebb7da5eb82
Author: Simon McVittie <smcv@debian.org>
Date: Wed Oct 8 11:57:13 2025 +0100
tests: Exercise GioUnix.FDMessage methods
Helps: https://gitlab.gnome.org/GNOME/pygobject/-/issues/719
Signed-off-by: Simon McVittie <smcv@debian.org>
commit 8bb5f208ebd62161c05835c3a6c497418a84b4d9
Author: Simon McVittie <smcv@debian.org>
Date: Wed Oct 8 11:03:17 2025 +0100
tests: Exercise all methods defined by GDesktopAppInfo
This is the most commonly-used object in GioUnix so it seems worthwhile
to test it more fully, especially if we need to add overrides for it.
Helps: https://gitlab.gnome.org/GNOME/pygobject/-/issues/719
Signed-off-by: Simon McVittie <smcv@debian.org>
commit af575c6dd62ee8d1887da6c1948b9524b0e41003
Author: Simon McVittie <smcv@debian.org>
Date: Wed Oct 8 11:03:47 2025 +0100
tests: Exercise the methods of GUnixInputStream, GUnixOutputStream
Helps: https://gitlab.gnome.org/GNOME/pygobject/-/issues/719
Signed-off-by: Simon McVittie <smcv@debian.org>
commit 25002fd6556b32bc1d401a8dcd1e9a1472c94da5
Author: Florian Müllner <fmuellner@gnome.org>
Date: Mon Sep 8 15:48:35 2025 +0200
importer: Excempt GioPlatform namespaces from require_version check
They are as tied to the GLib/GObject versions as Gio (and even
pygobject itself), so exempt them from the need to explicitly
calling gi.require_version() on first use.
Notably since commit 6a234a92b1b we import the platform namespace
ourselves without specifying a version first, so this also fixes
a warning when simply importing Gio.
commit 97a5e8accb2310efb9015568900347956ca75ed2
Author: Marco Trevisan <mail@3v1n0.net>
Date: Sun Sep 21 15:51:45 2025 +0200
gi/overrides/Gio: Do not skip symbols both in Gio and in platform specific
commit b6985e098d4ecd46eaa12814851ae4166b97393c
Author: Arjan Molenaar <gaphor@gmail.com>
Date: Sun Oct 12 10:28:42 2025 +0200
backport: gi/overrides/Gio: Use Platform prefix for platform-only symbols
Backport of 2e23b366dcb7aa18451d8bb6e5377beadf0c5a3b
In previous versions of GLib, platform-specific symbols such as
GUnixMountMonitor were mapped in the Gio namespace as Gio.UnixMountMonitor,
while since commit 6a234a92 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
See: gjs!1027
commit 1885e1bb9e68b6eef9d0da590ca27b8224078a88
Author: Arjan Molenaar <gaphor@gmail.com>
Date: Sun Oct 12 11:19:30 2025 +0200
Pin flatpak builds to GNOME 48
Changes in GLib make the flatpak builds fail. To make the tests
more stable we pin the GNOME version to the latest working version.
commit e7dface967b8fc8498558bb32c0927b0f7dded05
Author: Arjan Molenaar <gaphor@gmail.com>
Date: Sat Jul 5 14:14:24 2025 +0200
backport: Test in a flatpak build
pixbuf loaders are sandboxed, so we need to test with a build command,
to ensure the sandbox is disabled.
See also: https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/986
commit f40a614068c9912fbf22fae62a7d3eb640549113
Author: Arjan Molenaar <gaphor@gmail.com>
Date: Sun May 25 15:54:04 2025 +0200
Update news with release date
commit d2a7cd675b53c2eaf9cbf086aa93c35ba09e49b8
Author: Arjan Molenaar <gaphor@gmail.com>
Date: Sat Apr 19 23:19:22 2025 +0200
Update NEWS
commit ae38604f8a98f6707b0721df4e93b5d932f92016
Author: Arjan Molenaar <gaphor@gmail.com>
Date: Sat Apr 19 22:42:21 2025 +0200
Add explicit compile command for windows builds
commit 509c60a4d45a7d70f357c32c9115bcbbb82766dd
Author: Arjan Molenaar <gaphor@gmail.com>
Date: Sat Apr 19 22:34:13 2025 +0200
Update test-msys2.sh to main version
Should fix the build.
commit 40360a298c1a22839134565bc5bffa71ff3892de
Author: Arjan Molenaar <gaphor@gmail.com>
Date: Sat Apr 19 22:02:49 2025 +0200
Fix processmixin test for Python 3.12
We do not have to upgrade Python 3.12 this way.
commit 908c88b46bf775c0b6576dfeb48b33c49ae7c1d8
Author: Arjan Molenaar <gaphor@gmail.com>
Date: Sat Apr 19 21:33:59 2025 +0200
Update build to resemble main build
commit d4ce3be12df97ea5645012affd0ab590bd90c723
Author: Arjan Molenaar <gaphor@gmail.com>
Date: Sat Apr 19 21:19:50 2025 +0200
Ignore flake8 issue for now
commit 3bb03bc5d095cf51c8605521fcc2ce8cad36995f
Author: Fiona Klute <fiona.klute@gmx.de>
Date: Tue Mar 25 13:29:04 2025 +0100
gi.events._Selector.get_map(): look up file objects by file descriptor
File objects and their underlying file descriptors must be treated as
equivalent for lookup, or one may incorrectly be treated as not
registered when the other was used for the registration, leading to
bugs.
commit f4b104a9c84b398c689a3c7a98786fb276f60dbb
Author: Fiona Klute <fiona.klute@gmx.de>
Date: Tue Mar 25 13:32:49 2025 +0100
Fix exception type for re-registering file object with selector
Fixes: #690
commit e81c4c0a485a5573a87545454da8b05a8ea7e300
Author: Christoph Reiter <reiter.christoph@gmail.com>
Date: Thu Sep 12 14:08:12 2024 +0200
version bump
Among the 2 debian patches available in version 3.50.2-1 of the package, we noticed the following issues:
![[bug history graph]](https://qa.debian.org/data/bts/graphs/p/pygobject.png){kind=link}