On Wed, Nov 5, 2025 at 5:43 PM David Mohammed <[email protected]> wrote: > That's an awful lot of work for something that has a longevity of max > 2 months - we are trying to get a final release out this year which > will include the pygobject and other changes. > I prefer to spend my time on more productive matters finishing up this > release rather than delaying yet again budgie 10.10. > If this means dropping budgie out of testing for a short time then fair > enough. > > The new wayland budgie needs to be assembled in experimental; once > tidied it can then migrate to unstable/testing in due course.
Thank you for your reply. Here's what I'm doing for Debian. Let me know if this is ok: - Uploading pygobject 3.54.5-6 where python3-gi has Breaks: budgie-desktop (<< 10.9.3-1.1~) - Ask the Debian Release team to remove budgie-desktop and its rdepends from Testing. + budgie-desktop + budgie-extras + budgie-indicator-applet + vala-panel-appmenu - The new pygobject would then migrate to Testing within a few days For Ubuntu, the new version of pygobject will autosync. Then, I think the options are: - Remove budgie-desktop from Resolute. Since Ubuntu Budgie is an official desktop flavor, I don't think this is plausible at all. I'm only mentioning it for completion and for contrast with Debian. - Have the pygobject transition be stuck until a version of budgie-desktop is uploaded that either fixes the issue or ignores the issue because the upload would bypass the versioned Breaks from pygobject Thank you, Jeremy Bícha
