From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute via buildroot <buildroot@buildroot.org>
Cc: Fiona Klute <fiona.klute@gmx.de>,
James Hilliard <james.hilliard1@gmail.com>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [Buildroot] [PATCH v6 1/4] package/python-gobject: fix event source registration with Python 3.13
Date: Fri, 30 May 2025 21:41:50 +0200 [thread overview]
Message-ID: <20250530214150.3bb4581d@windsurf> (raw)
In-Reply-To: <20250523121521.380704-1-fiona.klute@gmx.de>
On Fri, 23 May 2025 14:15:18 +0200
Fiona Klute via buildroot <buildroot@buildroot.org> wrote:
> From: "Fiona Klute (WIWA)" <fiona.klute@gmx.de>
>
> Since Python 3.13 BaseSelectorEventLoop.add_reader() and
> BaseSelectorEventLoop.add_writer() use the mapping returned by
> selector.get_map() to detect if a file object is already
> registered. This fails with the implementation in gi.events._Selector
> if some calls use a file object, and others the raw file descriptor.
>
> Full upstream bug report:
> https://gitlab.gnome.org/GNOME/pygobject/-/issues/689
>
> This bug breaks package/python-aiomqtt, because its client object uses
> file objects in some places for the connection socket, and the file
> descriptor in others. The result is that the connection attempt times
> out because source registration fails, and the Future that marks
> successful connection never resolves.
>
> This commit adds the fix as backported to PyGObject 3.50 [1] so it can
> be cherry-picked to Buildroot stable versions using that version.
>
> [1] https://gitlab.gnome.org/GNOME/pygobject/-/merge_requests/423
>
> Signed-off-by: Fiona Klute (WIWA) <fiona.klute@gmx.de>
> ---
> Change v4 -> v5: Reorder patch before version bump to support backport
> to stable, replace patch with version applicable to 3.50.
Applied to master and cherry-picked into next so that I can apply the
remainder of the series on next. Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-05-30 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 12:15 [Buildroot] [PATCH v6 1/4] package/python-gobject: fix event source registration with Python 3.13 Fiona Klute via buildroot
2025-05-23 12:15 ` [Buildroot] [PATCH v6 2/4] package/python-gobject: bump version to 3.52.3 Fiona Klute via buildroot
2025-05-30 19:42 ` Thomas Petazzoni via buildroot
2025-05-23 12:15 ` [Buildroot] [PATCH v6 3/4] package/gobject-introspection: bump version to 1.84.0 Fiona Klute via buildroot
2025-05-30 19:44 ` Thomas Petazzoni via buildroot
2025-05-23 12:15 ` [Buildroot] [PATCH v6 4/4] package/libglib2: bump version to 2.84.2 Fiona Klute via buildroot
2025-05-30 19:46 ` Thomas Petazzoni via buildroot
2025-05-30 19:41 ` Thomas Petazzoni via buildroot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250530214150.3bb4581d@windsurf \
--to=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
--cc=fontaine.fabrice@gmail.com \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox