Bug 1671744

Summary:	Rebase libraw to 0.19.5
Product:	Red Hat Enterprise Linux 8	Reporter:	Debarshi Ray <debarshir>
Component:	LibRaw	Assignee:	Debarshi Ray <debarshir>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.1	CC:	jkoten, mclasen, rschiron, tpelka, vanhoof
Target Milestone:	rc	Keywords:	Rebase, Reopened
Target Release:	8.0	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	LibRaw-0.19.5-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 16:09: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:
Bug Depends On:	1681681
Bug Blocks:	1661555, 1663964

Description Debarshi Ray 2019-02-01 14:13:30 UTC

We should rebase LibRaw to the next bug-fix release in the 0.19.x series to pick up the usual assortment of fixes.

Note that RHEL 7.x already has LibRaw 0.19.2, and RHEL 8 currently has 0.19.1. Hence this should be very safe.

Comment 4 Debarshi Ray 2019-08-14 17:15:10 UTC

This seems to have been closed by mistake.

We should now be rebasing LibRaw to 0.19.4, which is being shipped in Fedoras >= 29.

Comment 5 Debarshi Ray 2019-10-30 16:09:42 UTC

(In reply to Debarshi Ray from comment #4)
> We should now be rebasing LibRaw to 0.19.4, which is being shipped in
> Fedoras >= 29.

The current version is 0.19.5.

Comment 6 Debarshi Ray 2019-10-30 16:21:57 UTC

*** Bug 1663138 has been marked as a duplicate of this bug. ***

Comment 7 Debarshi Ray 2019-10-30 16:23:33 UTC

Built LibRaw-0.19.5-1.el8:
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=24340361

Comment 8 Debarshi Ray 2019-10-30 16:33:51 UTC

*** Bug 1671034 has been marked as a duplicate of this bug. ***

Comment 12 errata-xmlrpc 2020-04-28 16:09: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-2020:1766