| 2022-06-30 20:13:27 |
Jeremy Bícha |
bug |
|
|
added bug |
| 2022-06-30 20:15:41 |
Jeremy Bícha |
nominated for series |
|
Ubuntu Jammy |
|
| 2022-06-30 20:15:41 |
Jeremy Bícha |
bug task added |
|
glib2.0 (Ubuntu Jammy) |
|
| 2022-06-30 20:15:46 |
Jeremy Bícha |
glib2.0 (Ubuntu Jammy): status |
New |
Triaged |
|
| 2022-06-30 20:15:49 |
Jeremy Bícha |
glib2.0 (Ubuntu Jammy): importance |
Undecided |
High |
|
| 2022-06-30 20:15:52 |
Jeremy Bícha |
glib2.0 (Ubuntu Jammy): assignee |
|
Jeremy Bicha (jbicha) |
|
| 2022-06-30 20:19:37 |
Jeremy Bícha |
description |
Impact
------ |
Impact
------
There is a new bugfix release in the stable 2.72 series
https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.3/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 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. |
|
| 2022-07-01 23:59:01 |
Launchpad Janitor |
glib2.0 (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2022-08-17 04:13:45 |
Chris Halse Rogers |
glib2.0 (Ubuntu Jammy): status |
Triaged |
Fix Committed |
|
| 2022-08-17 04:13:47 |
Chris Halse Rogers |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2022-08-17 04:13:49 |
Chris Halse Rogers |
bug |
|
|
added subscriber SRU Verification |
| 2022-08-17 04:13:53 |
Chris Halse Rogers |
tags |
jammy upgrade-software-version |
jammy upgrade-software-version verification-needed verification-needed-jammy |
|
| 2022-09-19 23:31:31 |
Jeremy Bícha |
tags |
jammy upgrade-software-version verification-needed verification-needed-jammy |
jammy upgrade-software-version verification-done verification-done-jammy |
|
| 2022-09-19 23:32:04 |
Jeremy Bícha |
tags |
jammy upgrade-software-version verification-done verification-done-jammy |
jammy upgrade-software-version verification-failed verification-failed-jammy |
|
| 2022-09-19 23:33:16 |
Jeremy Bícha |
bug watch added |
|
https://gitlab.gnome.org/GNOME/glib/-/issues/2687 |
|
| 2022-09-22 09:58:43 |
Łukasz Zemczak |
glib2.0 (Ubuntu Jammy): status |
Fix Committed |
Confirmed |
|
| 2022-09-22 09:58:46 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2022-10-12 19:25:57 |
Jeremy Bícha |
summary |
Update glib to 2.72.3 |
Update glib to 2.72.4 |
|
| 2022-10-12 19:26:03 |
Jeremy Bícha |
description |
Impact
------
There is a new bugfix release in the stable 2.72 series
https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.3/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 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. |
Impact
------
There is a new bugfix release in the stable 2.72 series
https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.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 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. |
|
| 2022-10-12 19:26:08 |
Jeremy Bícha |
glib2.0 (Ubuntu Jammy): status |
Confirmed |
In Progress |
|
| 2022-10-21 11:41:54 |
Timo Aaltonen |
glib2.0 (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2022-10-21 11:41:56 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2022-10-21 11:42:00 |
Timo Aaltonen |
tags |
jammy upgrade-software-version verification-failed verification-failed-jammy |
jammy upgrade-software-version verification-needed verification-needed-jammy |
|
| 2022-11-29 20:34:16 |
Jeremy Bícha |
tags |
jammy upgrade-software-version verification-needed verification-needed-jammy |
jammy upgrade-software-version verification-done verification-done-jammy |
|
| 2022-11-30 17:09:43 |
Launchpad Janitor |
glib2.0 (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2022-11-30 17:09:47 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
