Bug 1247511

Summary: Update chromium-browser to 44.0.2403.125
Product: Red Hat Enterprise Linux 6 Reporter: Tomas Popela <tpopela>
Component: chromium-browserAssignee: Tomas Popela <tpopela>
Status: CLOSED CURRENTRELEASE QA Contact: Tomas Pelka <tpelka>
Severity: high Docs Contact:
Priority: high    
Version: 6.8CC: bgollahe, gsgatlin, jreznik
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: chromium-browser-44.0.2403.125-1.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1247906 (view as bug list) Environment:
Last Closed: 2016-09-14 13:14:49 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:    
Bug Blocks: 1247906    

Description Tomas Popela 2015-07-28 08:09:55 UTC
Description of problem:
Update chromium-browser to latest upstream release - 44.0.2403.107. See changelog[0] and official announcement[1] for more information.

[0] - https://chromium.googlesource.com/chromium/src/+log/44.0.2403.89..44.0.2403.107?pretty=fuller&n=10000

[1] - http://googlechromereleases.blogspot.cz/2015/07/stable-channel-update_24.html

Comment 1 Tomas Popela 2015-07-29 05:49:29 UTC
Another update was released meantime, let's re-use this bug.

Update chromium-browser to latest upstream release - 44.0.2403.125. See changelog[0] and official announcement[1] for more information.

[0] - https://chromium.googlesource.com/chromium/src/+log/44.0.2403.107..44.0.2403.125?pretty=fuller&n=10000

[1] - http://googlechromereleases.blogspot.cz/2015/07/stable-channel-update_28.html

Comment 3 Gary Gatling 2015-08-05 21:38:29 UTC
I notice there is a chromium 44.0.2403.130 source released yesterday.

Comment 4 Marcel Kolaja 2016-09-14 13:14:49 UTC
The fix for this bug has been delivered in RHEL 6.7.z and this component has not been updated in RHEL 6.8. RHEL 6.8 contains the fix from RHEL 6.7.z. Therefore, this bug has been closed as CURRENTRELEASE.