Ubuntu
glib2.0 package

Update glib to 2.76.4

  1. Lunar (23.04)
  2. Bug #2028082
Bug #2028082 reported by Jeremy Bícha
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
glib2.0 (Ubuntu)
Fix Released
High
Unassigned
Lunar
Fix Committed
High
Jeremy Bícha

Bug Description

Impact
------
There is a new bugfix release in the stable 2.76 series

The current release in Ubuntu 23.04 is 2.76.1

https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS

Test Case 1
-----------
glib has an extensive test suite.

Failing tests will fail the build.
This update will also trigger a lot of autopkgtests.

Ensure that there aren't autopkgtest regressions triggered by this update and that the builds complete successfully

Test Case 2
-----------
Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser

What Could Go Wrong
-------------------
This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time.

Other Info
----------
The upstream gnome-remote-desktop maintainer requested that we do this update to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com

See original description
Jeremy Bícha (jbicha)
Changed in glib2.0 (Ubuntu Lunar):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Jeremy Bícha (jbicha)
Revision history for this message
Robie Basak (racb) wrote :

There's an open question on glib2.0 and the GNOME MRE here: https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/65?u=rbasak

Revision history for this message
Jeremy Bícha (jbicha) wrote :

I believe I have answered the question there.

Steve Langasek (vorlon)
description: updated
Revision history for this message
Chris Halse Rogers (raof) wrote : Please test proposed package

Hello Jeremy, or anyone else affected,

Accepted glib2.0 into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.76.4-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in glib2.0 (Ubuntu Lunar):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-lunar
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (glib2.0/2.76.4-0ubuntu1)

All autopkgtests for the newly accepted glib2.0 (2.76.4-0ubuntu1) for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

adsys/0.11.0 (arm64)
balsa/2.6.4-2 (arm64)
cmake-extras/1.6-1 (armhf)
firewalld/1.3.0-1 (arm64)
libsoup3/3.4.0-1 (amd64)
slurm-wlm/22.05.8-3 (armhf)
surf/2.1+git20221016-4build1 (armhf)
udisks2/2.9.4-4 (ppc64el)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/lunar/update_excuses.html#glib2.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Sebastien Bacher (seb128) wrote :

The autopkgtests issues listed earlier have been resolved with retries now

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.