Debian Bug report logs - #1118497
pluma: not compatible with pygobject >= 3.52

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: pluma: not compatible with pygobject >= 3.52

Date: Tue, 21 Oct 2025 12:35:42 +0100

[Message part 1 (text/plain, inline)]

Package: pluma
Version: 1.26.1-2.1
Severity: important
Tags: patch upstream forky sid
X-Debbugs-Cc: pygobject@packages.debian.org
Control: block 1118363 by -1

pygobject >= 3.52 (available in experimental) has switched from 
libgirepository-1.0 to libgirepository-2.0 as its way to access GObject 
libraries such as GTK.

libgirepository-1.0 and libgirepository-2.0 can be installed on the same 
system, but they cannot both be used within the same process, because 
they both register a GObject type named "GIRepository". This means that 
pygobject, libpeas, and apps like pluma all need to agree on which version 
they are going to use.

As a result we need to do a coordinated transition from:

    pygobject 3.50.x
    older libpeas
    older pygobject-dependent apps

to:

    pygobject >= 3.52
    libpeas >= 1.36.0-6~
    newer pygobject-dependent apps

The symptom is that if you start pluma on a system that has the versions of 
pygobject and libpeas from experimental:

    sudo apt install libgirepository-2.0-0 pluma
    sudo apt install python3-gi{,-cairo}/experimental libpeas-1.0-0/experimental gir1.2-peas-1.0/experimental
    pluma /etc/os-release

it won't start, with messages similar to those below:

>** (pluma:14121): WARNING **: 12:13:10.775: Could not load Peas repository: Typelib file for namespace 'GIRepository', version '3.0' not found
>** (pluma:14121): WARNING **: 12:13:10.776: Could not load PeasGtk repository: Typelib file for namespace 'GIRepository', version '3.0' not found
>(pluma:14121): GLib-GObject-CRITICAL **: 12:13:10.787: cannot register existing type 'GIRepository'
>(pluma:14121): GLib-CRITICAL **: 12:13:10.787: g_once_init_leave_pointer: assertion 'result != 0' failed
>(pluma:14121): GLib-GObject-CRITICAL **: 12:13:10.787: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
>(pluma:14121): GLib-GObject-CRITICAL **: 12:13:10.787: g_object_add_weak_pointer: assertion 'G_IS_OBJECT (object)' failed
>(pluma:14121): GLib-CRITICAL **: 12:13:10.787: g_once_init_leave: assertion 'result != 0' failed
>(pluma:14121): GLib-GObject-CRITICAL **: 12:13:10.787: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

For GNOME apps, a similar issue is fixed in the latest experimental 
uploads of eog, gedit, rhythmbox and totem, but now we need to do the 
same for non-GNOME apps as well.

To resolve this in experimental, please apply the attached patches and 
upload to experimental (or the GNOME team can NMU this for you if 
required, please let us know). Do not upload to unstable at this stage: 
it will not work.

For your convenience the patches are also available from:

    git fetch https://salsa.debian.org/smcv/pluma.git wip/smcv/libgirepository-2.0

and I will update that location with the bug number when I receive it. 
I'd have sent a merge request, but they are not currently enabled for 
this package's git repo.

After we get a transition slot from the release team, we will need to 
include pluma in a coordinated upload to unstable of pygobject, libpeas 
and several affected apps. Again, this can either be a maintainer upload 
or an NMU.

(The patch to the upstream source was taken from Fedora, which has 
already done the equivalent of this transition; thanks to Leigh Scott.)

Thanks,
    smcv

[0001-Build-with-a-libpeas-that-uses-libgirepository-2.0.patch (text/x-diff, attachment)]

[0002-Update-changelog.patch (text/x-diff, attachment)]

Message #12 received at 1118497@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: 1118497@bugs.debian.org

Subject: Re: Bug#1118497: pluma: not compatible with pygobject >= 3.52

Date: Tue, 28 Oct 2025 16:17:49 +0000

[Message part 1 (text/plain, inline)]

On Tue, 21 Oct 2025 at 12:35:42 +0100, Simon McVittie wrote:
>To resolve this in experimental, please apply the attached patches and
>upload to experimental (or the GNOME team can NMU this for you if
>required, please let us know). Do not upload to unstable at this stage:
>it will not work.
>
>For your convenience the patches are also available from:
>
>    git fetch https://salsa.debian.org/smcv/pluma.git wip/smcv/libgirepository-2.0

Updated patches attached for the recent pluma upload.

    smcv

[0001-Build-with-a-libpeas-that-uses-libgirepository-2.0.patch (text/x-diff, attachment)]

[0002-Update-changelog.patch (text/x-diff, attachment)]

Message #17 received at 1118497@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: 1118497@bugs.debian.org

Subject: Re: Bug#1118497: pluma: not compatible with pygobject >= 3.52

Date: Wed, 5 Nov 2025 12:10:38 +0000

Control: severity -1 serious

On Tue, 21 Oct 2025 at 12:35:42 +0100, Simon McVittie wrote:
>pygobject >= 3.52 (available in experimental) has switched from
>libgirepository-1.0 to libgirepository-2.0 as its way to access GObject
>libraries such as GTK.

We've started this transition in unstable, so pluma is about to become 
uninstallable. Please apply the patches I proposed previously, or 
something similar.

I'll try to NMU at the weekend if necessary.

    smcv

Message #24 received at 1118497-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 1118497-close@bugs.debian.org

Subject: Bug#1118497: fixed in pluma 1.28.0-2

Date: Wed, 05 Nov 2025 15:16:36 +0000

[Message part 1 (text/plain, inline)]

Source: pluma
Source-Version: 1.28.0-2
Done: Jeremy Bícha <jbicha@ubuntu.com>

We believe that the bug you reported is fixed in the latest version of
pluma, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1118497@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha <jbicha@ubuntu.com> (supplier of updated pluma package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 05 Nov 2025 09:34:39 -0500
Source: pluma
Built-For-Profiles: noudeb
Architecture: source
Version: 1.28.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian+Ubuntu MATE Packaging Team <debian-mate@lists.debian.org>
Changed-By: Jeremy Bícha <jbicha@ubuntu.com>
Closes: 1118497
Changes:
 pluma (1.28.0-2) unstable; urgency=medium
 .
   * Team upload
 .
   [ Simon McVittie ]
   * d/control: Build with a libpeas that uses libgirepository-2.0.
     - d/p/1001-Rebuild-for-libpeas1-changes.patch:
       Add patch from Fedora to enable that.
       (Helps: #1099164, #1118363) (Closes: #1118497)
 .
   [ Jeremy Bícha ]
   * Add Depends: python3-six for Snippets plugin
Checksums-Sha1:
 66fe8b79def7f63ebf44d5169695676a0fef32b3 2660 pluma_1.28.0-2.dsc
 8d3b87404c52d3ff6e39e870982c5b3638c80621 21304 pluma_1.28.0-2.debian.tar.xz
 6336d9bd6b53ad0d3a4fba4732f03086fa093476 17124 pluma_1.28.0-2_source.buildinfo
Checksums-Sha256:
 f21168f22e095b10645f99eb491a9f5487886cdf3b773370efebd62f51c59341 2660 pluma_1.28.0-2.dsc
 9f5b2e2d9e625288d59a1fbaef7c1a0edf41f1420a03ec763fa545ef4d1e2c7d 21304 pluma_1.28.0-2.debian.tar.xz
 04090acabb16cbbf600356ceee4bd603614ae026eb7dfbf54101f3e6eae2cafc 17124 pluma_1.28.0-2_source.buildinfo
Files:
 45be8fdd123f95c24021ce0a65345385 2660 x11 optional pluma_1.28.0-2.dsc
 0941ccc1208a1dababc4d7f31f9237a2 21304 x11 optional pluma_1.28.0-2.debian.tar.xz
 374a89edd505faae4b7b321c6e7d30da 17124 x11 optional pluma_1.28.0-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmkLYLMACgkQ5mx3Wuv+
bH0/uBAAnIBEEQKhIXr40gFf9/uELVF+wKGuvgUKYujIdPiAMnhhiK0A/sn+4WBt
ZSAX3OY0IyQwneSWYpw6bDF2icC3zGDju4RSFzI8cGFf3KP4DOcmIArqd2gxjDsa
J2wNyCT3KOGHQBcN63V/SvGnB6PtDbzc6hwvHk7OyZk3H3BERJj3DPsean2sHrYN
+jMREdvwENKQv/4mpGpC+N/rziAL+oime7wxwoVQ81Y3cWr1AFJPMLFQ6B1/UTTT
ckCxyXvJhcAHWayuwR+he2JMX8Wg81OR2Urp/B7iizSCn+WqdC/Zi0aupSLJOVwp
x+ZS0xxgr0zd+X9Mrftw43jYpZAbBL2iJUQns0EBd+N6A2Xr5c5aaz9Zsv2O0mL0
G7Q9QlGV2xioYWMCz2I2jgzXXSMcxHi1++k0gbzftYU6phApx6j1drT96P1+rlAs
1E9RKKDABJmh8mgpJYIiHUZRXCeCzKt6CJ9NRRqIpKKAHtQfdV2knDYvyv+9RTvm
BvJFoiusGXpO7MEcUjUxRDTmO7thkZV+FBbtwNhPc741ifbNcH4iHvj2f1f90Fna
Oln48iEUDGdJSMPTIhfXfPBjL9+7IMrwKZ4xploiE8+ZFBQO1P6aU0alpD+0pyO9
gtb0sonbQAtWaoqjRFSVXiuBWUuZCH4VOET4JPW8jzE0ShnqdHA=
=XEkW
-----END PGP SIGNATURE-----

[Message part 2 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.