Bug 1369526

Summary:	Rebase pidgin to a newer upstream release
Product:	Red Hat Enterprise Linux 7	Reporter:	Debarshi Ray <debarshir>
Component:	pidgin	Assignee:	Debarshi Ray <debarshir>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	bgollahe, mcepl, ricardo.arguello, tpelka
Target Milestone:	rc	Keywords:	Rebase
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 20:20:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Debarshi Ray 2016-08-23 16:27:23 UTC

While we are shipping pidgin 2.10.7 in RHEL 7.3, there have been a few upstream releases with bug-fixes and features that could be interesting for us. There are also a few security fixes that we can pick up. See:
https://bitbucket.org/pidgin/www/src/tip/htdocs/ChangeLog
http://pidgin.im/news/security/

I'd suggest that we rebase it to at least 2.10.11, since it doesn't have an API changes from 2.10.7. If possible (ie. telepathy-purple, pidgin-sipe continue to work) we should go all the way to 2.11.0.

Comment 1 Tomas Pelka 2016-08-23 16:37:31 UTC

Just and idea, can we do it in 7.3?

Comment 2 Debarshi Ray 2016-08-25 13:35:55 UTC

(In reply to Tomas Pelka from comment #1)
> Just and idea, can we do it in 7.3?

Sure. If you are willing to test it, I am willing to rebase it. :)

Comment 4 Debarshi Ray 2016-12-01 13:53:48 UTC

Sad. I already did the work to rebase it in August, and was hoping it could make it to RHEL 7.4.

Comment 6 Debarshi Ray 2017-01-09 13:17:14 UTC

I have built pidgin-2.10.11-1.el7:
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=12316343

Comment 8 Matěj Cepl 2017-05-16 19:08:52 UTC

Rebase happened.

Comment 9 errata-xmlrpc 2017-08-01 20:20:06 UTC

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://access.redhat.com/errata/RHSA-2017:1854