Update glib to 2.72.4

[Jeremy Bícha]

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.

[Launchpad Janitor (janitor)]

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

[Chris Halse Rogers (raof)]

Hello Jeremy, or anyone else affected,

Accepted glib2.0 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.72.3-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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

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

systemd/249.11-0ubuntu3.4 (armhf)
flatpak/1.12.7-1 (arm64)
libaperture-0/0.1.0+git20200908-3 (armhf)
automake-1.16/1:1.16.5-1.3 (arm64)
booth/1.0-237-gdd88847-4ubuntu2.2 (armhf)

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/jammy/update_excuses.html#glib2.0

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

Thank you!

[Sebastien Bacher (seb128)]

The autopkgtest issue resolved on retry and can be ignored

[Jeremy Bícha (jbicha)]

There is a regression introduced in the 2.72.3 update so we're going to prepare 2.72.4 for Jammy when it's released.

https://gitlab.gnome.org/GNOME/glib/-/issues/2687

[Łukasz Zemczak (sil2100)]

The version of glib2.0 in the proposed pocket of Jammy that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days.

[Timo Aaltonen (tjaalton)]

Hello Jeremy, or anyone else affected,

Accepted glib2.0 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.72.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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

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

systemd/249.11-0ubuntu3.6 (amd64)
apport/2.20.11-0ubuntu82.1 (amd64)
notify-osd/0.9.35+20.04.20191129-0ubuntu2 (amd64)
swtpm/0.6.3-0ubuntu3 (amd64)
automake-1.16/1:1.16.5-1.3 (amd64)
gvfs/1.48.2-0ubuntu1 (ppc64el, amd64)

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/jammy/update_excuses.html#glib2.0

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

Thank you!

[Jeremy Bícha (jbicha)]

The autopkgtests completed successfully.

I installed glib 2.72.4-0ubuntu1 on Ubuntu 22.04 LTS. I logged out and logged back in and verified that the desktop works and the terminal, file browser, and epiphany-browser work normally.

[Launchpad Janitor (janitor)]

This bug was fixed in the package glib2.0 - 2.72.4-0ubuntu1

---------------
glib2.0 (2.72.4-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1980408)
  * Update testfilemonitor-Skip-if-we-are-avoiding-flaky-tests.patch
    for new testfilemonitor test.

 -- Jeremy Bicha <email address hidden> Wed, 12 Oct 2022 14:59:04 -0400

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for glib2.0 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.