[SRU] 2.60.3

disco in queue, will sync eoan once lp picks it up

This bug was fixed in the package glib-networking - 2.60.3-1

---------------
glib-networking (2.60.3-1) experimental; urgency=medium

  * New upstream release (LP: #1832458)
    - Fix clobbering of the thread-default main context after certificate
      verification failure during async handshakes since 2.60.1
    - Fix GTlsDatabase initialization failures in OpenSSL backend due to
      uninitialized memory use
    - Fix minor leak of ALPN protocols
    - OpenSSL backend now defaults to system trust store
    - Fix client auth failure error with GnuTLS 3.6.7
  * gnutls-Handle-new-GNUTLS_E_CERTIFICATE_REQUIRED.patch: Drop. It's in this
    upstream release.

 -- Iain Lane <email address hidden> Wed, 12 Jun 2019 09:21:12 +0100

Hello Iain, or anyone else affected,

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

I verified 2.60.3-1~ubuntu19.04.1 according to the first post.

This bug was fixed in the package glib-networking - 2.60.3-1~ubuntu19.04.1

---------------
glib-networking (2.60.3-1~ubuntu19.04.1) disco; urgency=medium

  * No-change backport from experimental / eoan to disco to SRU this
    stable update.

glib-networking (2.60.3-1) experimental; urgency=medium

  * New upstream release (LP: #1832458)
    - Fix clobbering of the thread-default main context after certificate
      verification failure during async handshakes since 2.60.1
    - Fix GTlsDatabase initialization failures in OpenSSL backend due to
      uninitialized memory use
    - Fix minor leak of ALPN protocols
    - OpenSSL backend now defaults to system trust store
    - Fix client auth failure error with GnuTLS 3.6.7
  * gnutls-Handle-new-GNUTLS_E_CERTIFICATE_REQUIRED.patch: Drop. It's in this
    upstream release.

 -- Iain Lane <email address hidden> Wed, 12 Jun 2019 10:12:46 +0100

The verification of the Stable Release Update for glib-networking 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.