Bug 1174446 – Rebase to 2.48.0

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1174446 - Rebase to 2.48.0

Summary:	Rebase to 2.48.0

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	libsoup (Show other bugs)
Sub Component:
Version:	7.2
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Dan Winship
QA Contact:	Desktop QE
Docs Contact:

URL:
Whiteboard:
Keywords:	Rebase

Depends On:
Blocks:	1149939 desktop-rebase
	Show dependency tree / graph

Reported:	2014-12-15 15:41 EST by Matthias Clasen
Modified:	2015-11-19 04:26 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:	libsoup-2.48.1-2.el7
Doc Type:	Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-11-19 04:26:56 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2015:2106	normal	SHIPPED_LIVE	desktop core libraries bug fix and enhancement update	2015-11-19 04:34:35 EST

Groups: None (edit)

Description Matthias Clasen 2014-12-15 15:41:43 EST

We are planning a desktop rebase to GNOME 3.14.x in 7.2. libsoup should be rebased to the latest stable release, probably 2.48.0.

Comment 8 errata-xmlrpc 2015-11-19 04:26:56 EST

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2106.html

Note You need to log in before you can comment on or make changes to this bug.