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.
Assignee: bugsquad => dmorganec
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
also valid for mga1
Component: RPM Packages => SecurityTarget Milestone: --- => Mageia 1
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.lepikHardware: i586 => AllVersion: Cauldron => 1Target Milestone: Mageia 1 => ---
(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
Hi, New release with some critical patches : 19.0.1084.52 See http://googlechromereleases.blogspot.com/2012/05/stable-channel-update_23.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+GoogleChromeReleases+%28Google+Chrome+Releases%29
We know those :-) That's not the issue. The issue is that it's hard to get proper sources for chromium.
Chromium 20.0.1132.47 has been pushed into Testing repo. Maybe it solves this bug report?
CC: (none) => olivier.delaune
yes and no, we need also an update in mga1
Version: 1 => 2Summary: 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-stableWhiteboard: (none) => MGA1TOO
yes still a build issue on mga1. I try to understand.
see bug 6679
Depends on: (none) => 6679
Depends on: 6679 => (none)
updates pushed
Status: NEW => RESOLVEDResolution: (none) => FIXED