Bug 5966 - Update chromium to the latest stable release (20.0.1132.47)
Summary: Update chromium to the latest stable release (20.0.1132.47)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Security (show other bugs)
Version: 2
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: D Morgan
QA Contact:
URL:
Whiteboard: MGA1TOO
Keywords:
Depends on: 6679
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-18 10:08 CEST by Raphaël Vinet
Modified: 2012-07-21 23:39 CEST (History)
4 users (show)

See Also:
Source RPM: chromium-browser-stable
CVE:
Status comment:


Attachments

Description Raphaël Vinet 2012-05-18 10:08:59 CEST
Description of problem:
I propose to update the chromium's package

We have the 18.0.1025.168-1.mga2 and the latest stable release is now the 19.0.1084.46 with some security patches

See http://googlechromereleases.blogspot.com/2012/05/stable-channel-update.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+GoogleChromeReleases+%28Google+Chrome+Releases%29

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Thierry Vignaud 2012-05-18 10:44:26 CEST

Assignee: bugsquad => dmorganec

Comment 1 Thierry Vignaud 2012-05-18 10:48:43 CEST
We could look at this:
http://rpm.pbone.net/index.php3/stat/4/idpl/18080522/dir/other/com/chromium-browser-stable-19.0.1084.47-1.i686.rpm.html

CC: (none) => thierry.vignaud

Comment 2 Manuel Hiebel 2012-05-19 00:27:30 CEST
also valid for mga1

Component: RPM Packages => Security
Target Milestone: --- => Mageia 1

Comment 3 Sander Lepik 2012-05-19 08:39:11 CEST
Is there any rule for filing security bugs if more than one verson is affected?
Should there be two bugs or how is it done? For some reason we can't choose two versions at the same time.

CC: (none) => sander.lepik
Hardware: i586 => All
Version: Cauldron => 1
Target Milestone: Mageia 1 => ---

Comment 4 Dave Hodgins 2012-05-19 09:34:00 CEST
(In reply to comment #3)
> Is there any rule for filing security bugs if more than one verson is affected?
> Should there be two bugs or how is it done? For some reason we can't choose two
> versions at the same time.

Separate bug reports should be opened.

CC: (none) => davidwhodgins

Comment 6 Thierry Vignaud 2012-05-24 22:02:24 CEST
We know those :-)
That's not the issue. The issue is that it's hard to get proper sources for chromium.
Comment 7 Olivier Delaune 2012-07-06 09:55:52 CEST
Chromium 20.0.1132.47 has been pushed into Testing repo. Maybe it solves this bug report?

CC: (none) => olivier.delaune

Comment 8 Manuel Hiebel 2012-07-06 10:31:06 CEST
yes and no, we need also an update in mga1

Version: 1 => 2
Summary: Update chromium to the lastest stable release (19.0.1084.46) => Update chromium to the latest stable release (20.0.1132.47)
Source RPM: chromium-browser-stable-18.0.1025.168-1.mga2.src.rpm => chromium-browser-stable
Whiteboard: (none) => MGA1TOO

Comment 9 D Morgan 2012-07-06 14:32:35 CEST
yes still a build issue on mga1. I try to understand.
Comment 10 Manuel Hiebel 2012-07-18 00:50:40 CEST
see bug 6679

Depends on: (none) => 6679

Manuel Hiebel 2012-07-18 00:51:22 CEST

Depends on: 6679 => (none)

Manuel Hiebel 2012-07-18 00:52:01 CEST

Depends on: (none) => 6679

Comment 11 Manuel Hiebel 2012-07-21 23:39:11 CEST
updates pushed

Status: NEW => RESOLVED
Resolution: (none) => FIXED


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