SRU 2.56.2 to bionic

Hello Marco, or anyone else affected,

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

No need to perform full verification as per GNOME exception (https://wiki.ubuntu.com/StableReleaseUpdates/GNOME)

The new glib2.0 upload seems to have a lot of autopkgtest regressions listed - could you take a look and assess which one of those can be real potential regressions? Thanks.

The network-monitor-race test is racy (amusingly). I retried and all except armhf tests pass. This is supposed to be fixed with 2.56.3 which is scheduled to be out soon (we'd want to check that is true before uploading). I propose that we let this one slide for this SRU.

udisks2 seems to have been broken by something else - the results triggered from cryptsetup also fail in the same way, so I think those are also Not Our Problem™.

I think/hope Marco's looking at the rest. Hopefully they are flaky and I'll retry any as necessary, just let me know.

Yeah, I confirmed that the glib2.0 armhf network-monitor-race test also fails on release. udisks2 is broken and I hinted it in. Others passed after some retried. Thanks for looking into that! Releasing!

This bug was fixed in the package glib2.0 - 2.56.2-0ubuntu0.18.04.1

---------------
glib2.0 (2.56.2-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #1789472, LP: #1764779)
  * Refreshed patches
  * d/p/tests-network-monitor-Always-use-the-dummy-proxy-res.patch:
    - Removed (aplied upstream)

 -- Marco Trevisan (Treviño) <email address hidden> Tue, 28 Aug 2018 13:25:36 -0500

The verification of the Stable Release Update for glib2.0 has completed successfully and the package has now been 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.

I did keep on looking at the armhf failure. I think that the netlink network monitor is a bit buggy and I filed https://gitlab.gnome.org/GNOME/glib/merge_requests/313 with some fixes to it.