[SRU] New stable release 2.48.2

Bug #1581480 reported by Iain Lane on 2016-05-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone
glib-networking (Ubuntu)
Bartosz Kosiorek

Bug Description

[ Description ]

Upstream have released a new bugfix release.

[ Changes ]

From NEWS:

  * gnutls: Fixed an infinite loop if a server sent two identical
    copies of its CA certificate [#765317, Carlos Garcia Campos]

[ QA, testing, regression potential ]

Under the GNOME MRE, you can believe all bugs upstream says are fixed are really fixed. Just test the system and make sure there are no regressions (e.g. look at errors.ubuntu.com).

Iain Lane (laney) wrote :

I uploaded this as a sync from yakkety/unstable. There are some packaging changes. I don't think they are bad to have in the SRU (dbg -> dbgsym with migration), but if you disagree then I can re-upload as just the upstream bump.

Changed in glib-networking (Ubuntu):
status: New → Fix Released
Changed in glib-networking (Ubuntu Xenial):
status: New → In Progress
Martin Pitt (pitti) wrote :

Can you please revert the dropping of glib-networking-dbg? Doing this in an SRU is too intrusive and we don't provide a proper upgrade path for this.

Iain Lane (laney) wrote :


Hello Iain, or anyone else affected,

Accepted glib-networking into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib-networking/2.48.2-1~ubuntu16.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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in glib-networking (Ubuntu Xenial):
status: In Progress → Fix Committed
tags: added: verification-needed
Changed in glib-networking (Ubuntu Xenial):
assignee: nobody → Bartosz Kosiorek (gang65)
Bartosz Kosiorek (gang65) wrote :

It is working perfectly for me after install glib-networking from proposed.

tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package glib-networking - 2.48.2-1~ubuntu16.04.1

glib-networking (2.48.2-1~ubuntu16.04.1) xenial; urgency=medium

  * Backport from yakkety/unstable to 16.04 (LP: #1581480), with one change
    - Keep the static -dbg package.

glib-networking (2.48.2-1) unstable; urgency=medium

  * New upstream release.
  * Install systemd user service for the glib-pacrunner D-Bus session service.

glib-networking (2.48.1-1) unstable; urgency=medium

  * New upstream release.
  * Drop glib-networking-dbg package now that we have automatic dbgsym
  * Ensure proper upgrade from glib-networking-dbg to new dbgsym packages by
    using dh_strip --dbgsym-migration. Bump Build-Depends on debhelper
  * Bump debhelper compatibility level to 9.
  * Bump Standards-Version to 3.9.8.

 -- Iain Lane <email address hidden> Wed, 18 May 2016 10:26:06 +0100

Changed in glib-networking (Ubuntu Xenial):
status: Fix Committed → Fix Released

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.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers