>= 
 15:19: 
 From: owner@bugs.debian.org 
  
 This is a multi-part message in MIME format... 
  
 Your message dated Wed, 05 Nov 2025 15:16:36 +0000 
 with message-id  
 and subject line Bug#1118497: fixed in pluma 1.28.0-2 
 has caused the Debian Bug report #1118497, 
 regarding pluma: 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 owner@bugs.debian.org 
 immediately.) 
  
  
 -- 
 1118497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118497 
 Debian Bug Tracking System 
 Contact owner@bugs.debian.org with problems 
  
 Received: (at submit) by bugs.debian.org; 21 Oct 2025 11:35:47 +0000 
 X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02 
  (2024-03-25) on buxtehude.debian.org 
 X-Spam-Level: 
 X-Spam-Status: No, score=-116.2 required=4.0 tests=BAYES_00, 
  BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID, 
  DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,FVGT_m_MULTI_ODD,GMAIL, 
  HAS_PACKAGE,MD5_SHA1_SUM,SPF_HELO_NONE,SPF_NONE,UNPARSEABLE_RELAY, 
  USER_IN_DKIM_WELCOMELIST autolearn=ham autolearn_force=no 
  version=4.0.1-bugs.debian.org_2005_01_02 
 X-Spam-Bayes: score:0.0000 Tokens: new, 62; hammy, 150; neutral, 369; 
 spammy, 
  0. spammytokens: 
  hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin, 
  0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311, 
  0.000-+--H*RT:311, 0.000-+--H*RT:108 
 Return-path:  
 Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:33976) 
  by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_ 
 SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) 
  (Exim 4.96) 
  (envelope-from ) 
  id 1vBAeY-00B3cS-24 
  for submit@bugs.debian.org; 
  Tue, 21 Oct 2025 11:35:46 +0000 
 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian. 
 org; 
  s=smtpauto.stravinsky; h=X-Debian-User:Content-Type:MIME-Version:Message- 
 ID: 
  Subject:To:From:Date:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: 
  Content-Description:In-Reply-To:References; 
  bh=Vw78CTAfWiCONnPTXJIGiiYO+noPgLUKWWmOzmgte5U=; b 
 =SilJq4JW4drABf+NZA8JTIEYbK 
  GX4gGrCoaVAl/iFZ5gGLtDguko+qaOLs9plWzMhya/K3+engAA 
 GlIZTURtDVRGx36lYYe7QLIVxMm 
  dkbYqfc5q9bJOLnhOmuTyg6ttCdDkxgW8um5Pe9QFKqkGp6d1y 
 5JG5IWSVWEEFIzSMVaMc3P/zvyW 
  B8YfQ3g16IcLl5WD0V4QujkoYjRU/pjGHMWj2liE9X5D/u/AVY 
 pVWgz8RPkUF6qBya0AfARX1CXur 
  ptklzWxtNbyWPnaNfKFfRu+J2zJ3ZyRkqRnHU4B5asnb/exiCA 
 hhxG8IipoDfJz33ayfLZywBGeSk 
  NY3tWg3Q==; 
 Received: from authenticated user 
  by stravinsky.debian.org with esmtpsa (TLS1.3:ECDH 
 E_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) 
  (Exim 4.94.2) 
  (envelope-from ) 
  id 1vBAeW-006Yl5-2I 
  for submit@bugs.debian.org; Tue, 21 Oct 2025 11:35:45 +0000 
 Date: Tue, 21 Oct 2025 12:35:42 +0100 
 From: Simon McVittie  
 To: Debian Bug Tracking System  
 Subject: pluma: not compatible with pygobject >= 3.52 
 Message-ID:  
 MIME-Version: 1.0 
 Content-Type: multipart/mixed; boundary="Du+bPdg7NrXZXPUl" 
 Content-Disposition: inline 
 X-Debian-User: smcv 
 Delivered-To: submit@bugs.debian.org 
  
  
 --Du+bPdg7NrXZXPUl 
 Content-Type: text/plain; charset=us-ascii 
 Content-Disposition: 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. 
  
  
 [continued in next message] 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)