Your message dated Wed, 05 Nov 2025 15:09:56 +0000
with message-id <[email protected]>
and subject line Bug#1118501: fixed in entangle 3.0-6
has caused the Debian Bug report #1118501,
regarding entangle: not compatible with pygobject >= 3.52
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1118501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118501
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: entangle
Version: 3.0-5
Severity: important
Tags: upstream forky sid
X-Debbugs-Cc: [email protected]
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 entangle 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 entangle on a system that has the versions of
pygobject and libpeas from experimental:
sudo apt install libgirepository-2.0-{0,dev} entangle
sudo apt install python3-gi{,-cairo}/experimental
libpeas-{1.0-0,dev}/experimental gir1.2-peas-1.0/experimental
entangle
(in the GUI) menu -> Preferences
the preferences dialog will not open, with messages like these:
>(entangle:16066): GLib-GObject-CRITICAL **: 12:52:53.847: cannot register
>existing type 'GIRepository'
>(entangle:16066): GLib-CRITICAL **: 12:52:53.847: g_once_init_leave_pointer:
>assertion 'result != 0' failed
>(entangle:16066): GLib-GObject-CRITICAL **: 12:52:53.847:
>g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
>(entangle:16066): GLib-GObject-CRITICAL **: 12:52:53.847:
>g_object_add_weak_pointer: assertion 'G_IS_OBJECT (object)' failed
>(entangle:16066): GLib-CRITICAL **: 12:52:53.847: g_once_init_leave: assertion
>'result != 0' failed
>(entangle:16066): GLib-GObject-CRITICAL **: 12:52:53.847: 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.
I expect that the necessary changes for this will be similar to those in
the experimental versions of eog, gedit, rhythmbox and totem, and
proposed for eom (#1118496) and pluma (#1118497). Initially, these
changes will need to be uploaded to experimental, either by a maintainer
or as an NMU.
After we get a transition slot from the release team, we will need to
include entangle in a coordinated upload to unstable of pygobject, libpeas
and several affected apps. Again, this can either be a maintainer upload
or an NMU.
Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: entangle
Source-Version: 3.0-6
Done: Jeremy Bícha <[email protected]>
We believe that the bug you reported is fixed in the latest version of
entangle, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jeremy Bícha <[email protected]> (supplier of updated entangle 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 05 Nov 2025 09:52:06 -0500
Source: entangle
Built-For-Profiles: noudeb
Architecture: source
Version: 3.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers
<[email protected]>
Changed-By: Jeremy Bícha <[email protected]>
Closes: 1118501
Changes:
entangle (3.0-6) unstable; urgency=medium
.
* Team upload
.
[ Simon McVittie ]
* d/patches: Be compatible with either older or newer versions of
libpeas (Helps: #1118363, #1118501)
* d/control: Build against new versions of libpeas, python3-gi.
python-gi-dev is now necessary at build time so that we can auto-detect
its version, because in Debian we've backported upstream changes targeted
at libpeas 1.38 into version 1.36, similar to what was done in Fedora.
(Helps: #1118363) (Closes: #1118501)
Checksums-Sha1:
3bae17b382ad679e6b7cb0309213ef158047c8d9 2616 entangle_3.0-6.dsc
fcbe825a8d57e491f0d841e601f49c22c10c4ba0 9108 entangle_3.0-6.debian.tar.xz
d96097acd81f28e0ed0581c99039bbff716cba4b 18454 entangle_3.0-6_source.buildinfo
Checksums-Sha256:
a75a742acf5b4ff5313ce88e1815fd947fb9efb7b60a852a2314586e624f1220 2616
entangle_3.0-6.dsc
dda4f2c4b5d19c3fc1b6c565280fb84ec38ca6cc9a0ed3097f2ff8ea349196ff 9108
entangle_3.0-6.debian.tar.xz
03f193c579e06f5338053c0268c8d411ccb4f843f422a4d94f051f42c59413e2 18454
entangle_3.0-6_source.buildinfo
Files:
a5c53ecb4714dbd25dd3ea8cef444bb1 2616 utils optional entangle_3.0-6.dsc
95a95ae31650eadeeea4449b9423ceda 9108 utils optional
entangle_3.0-6.debian.tar.xz
843ac3307c96378d66f10b7b3e1f7a55 18454 utils optional
entangle_3.0-6_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmkLZP8ACgkQ5mx3Wuv+
bH3Dug/9HSTApcFr/YY7frZDVjm9ygPmhw3wqG4kxHEVGCIwLUDiOgRXswXzxNdn
uf4qLAjUEtzGtXx3ruikT3GyBrsfR4Ho8XiVC5FzifwPtLPEAddotwc1RS1P9NTh
uS5zjNm0g1vtW2IAT6A0c7b3sgAm3q6gaYTuofvmP23MBZHgeyD3RwxB5jEm1PCj
2qzTjN+2kBRYdo8U94Unb+xoENl8178ppz9gM9/768GMm+pMQWsSVxgAPa9QGgsa
MG5z/7XojO/7LVxDDkbL9tGpV6iq4NjOSz7YrTA8EWDqJRMqdNcLQolGQMHruCvU
wBSl3oUGEQ6NQLZaVs23CYOUa1ri6eV1EqFCgikTo6QiMEIRUSMFmcrQBBTQex80
55boWuC1JZ7Ejk/EAcxmqmNTLVgHlP/cSC+vxXbx0cTJ2BFcOEncDwt9Jh5y27fu
4tse7syvyq2Z1d3GEEU5nZSlBDgHiZ7qH2ZkRKawFcOAp35p13Mh66AsnkvvJUai
D4dRGKYCJlZFgsAEH4F9l+lneQKeRq+8zXslpmFTKHxGjh0HgOPI7sUnEv46arks
f6dnGQOzvH8x172eVbBz0DcjmgnXocFuzL+5GtOkCW4wABVJo3P/mjmsNEHcL9Az
rz4EPl9nozrDgOrx7w/aZ9lvkKpzMOBC+SQ02gF+DAP68yAKyY4=
=zwaA
-----END PGP SIGNATURE-----
pgpwvpbAhvqkC.pgp
Description: PGP signature
--- End Message ---
