Update glib to 2.72.4
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glib2.0 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Jammy |
Fix Released
|
High
|
Jeremy Bícha |
Bug Description
Impact
------
There is a new bugfix release in the stable 2.72 series
https:/
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 autopgktest 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.
Changed in glib2.0 (Ubuntu Jammy): | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Jeremy Bicha (jbicha) |
description: | updated |
summary: |
- Update glib to 2.72.3 + Update glib to 2.72.4 |
description: | updated |
Changed in glib2.0 (Ubuntu Jammy): | |
status: | Confirmed → In Progress |
This bug was fixed in the package glib2.0 - 2.72.3-1
---------------
glib2.0 (2.72.3-1) unstable; urgency=medium
* New upstream release (LP: #1980408)
* Drop GFileMonitor patches applied in new release
-- Jeremy Bicha <email address hidden> Thu, 30 Jun 2022 16:12:12 -0400