[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1118613: marked as done (transition: pygobject 3.54)

Your message dated Thu, 13 Nov 2025 23:18:05 +0100
with message-id <99afb82d-3f0b-4ab1-989a-c9a9c5afbe3c@debian.org>
and subject line Re: Bug#1118613: transition: pygobject 3.54
has caused the Debian Bug report #1118613,
regarding transition: pygobject 3.54
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.)


-- 
1118613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118613
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: pygobject@packages.debian.org
Control: affects -1 + src:pygobject
User: release.debian.org@packages.debian.org
Usertags: transition

pygobject >= 3.52 has switched from libgirepository-1.0 to
libgirepository-2.0 as its way to access GObject libraries such as GTK, 
resulting in a transition being needed. I think we're ready for this 
now, and I think it can happen either before or after GNOME 49 (which is 
blocked by #1116563).

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 some apps all need to agree on which version 
they are going to use (and unfortunately versioned symbols would not 
help here either).

This will need a coordinated upload of these GNOME team packages, all of 
which have versions in experimental that can be re-uploaded to unstable:

* pygobject (#1099164)
* libpeas (#1118363), but not libpeas2
* eog (no bug)
* gedit (no bug)
* rhythmbox (no bug)
* totem (no bug)

These non-GNOME packages have patches available and will need either 
uploading to unstable or removing from testing:

* entangle (#1118501)
* eom (#1118496)
* liferea (#1118500)
* pluma (#1118497)

I expect that the autoradio package will also regress with the new 
pygobject (#1118278) because it uses the pygtkcompat compatibility layer 
for migrating from pygobject 2 to 3, which was finally removed in 3.54. 
I don't have a patch for this.

In the next upload of the new pygobject I intend to add versioned Breaks 
on the known-broken packages, with the assumption that their next upload 
will fix the incompatibility, unless the release team would prefer not 
to have those Breaks.

Finally, glib2.0 (>= 2.86.0-7) will need to migrate first, to avoid 
regressions in packages like ibus-anthy and isenkram that need typelibs 
from the legacy non-multiarch directory. The next upload of the new 
pygobject will add a versioned dependency to make sure that the fixed 
glib2.0 is ready first, and it should migrate in a few days anyway.

These packages depend on both python3-gi and either 
libgirepository-1.0-1 or gir1.2-girepository-2.0, but don't appear to 
need any changes:

* blueprint-compiler
* cinnamon
* endeavour
* exaile
* gnome-builder
* gnome-music
* gtk-meshtastic-client
* pympress
* rednotebook

Thanks,
    smcv

--- End Message ---
--- Begin Message --- 
On 07/11/2025 16:55, Jeremy Bícha wrote:

On Wed, Nov 5, 2025 at 7:05 AM Simon McVittie <smcv@debian.org> wrote:

When everything is ready to migrate, the release team will need to
remove these packages from testing:

* autoradio (#1118278)
* streamtuner2 (#1094922)


In addition to those 2 removals, we identified that our pre-upload
analysis of budgie-desktop missed a major incompatibility. With the
approval of Debian's Budgie maintainer (#1120138) , we request that
these additional packages be removed from Testing (budgie-desktop and
its rdepends):
* budgie-desktop
* budgie-extras
* budgie-indicator-applet
* vala-panel-appmenu


I have added the necessary removal hints, and pygobject has migrated.

Cheers,
Emilio

--- End Message ---
Reply to: