Description of problem: Updating from 16.0.912.63 to the last stable release 17.0.963.46 ==> http://googlechromereleases.blogspot.com/search/label/Stable%20updates Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
Hi, thanks for the bug report. As there is some CVEs indeed we need updating the new release (the same as firefox, before the ESR version)
CC: (none) => thierry.vignaudComponent: RPM Packages => SecuritySource RPM: (none) => chromium-browser-stable
Assignee: bugsquad => dmorganec
Ping ?
Note that 17.0.963.65 was released today. http://googlechromereleases.blogspot.com/2012/03/chrome-stable-update.html
CC: (none) => davidwhodgins
Just uploaded into cauldron
Ping! I have addon complaining that it won't work soon if i don't update my browser. AFAIK version 18 is already released.. Are we going to update this thing or should we drop it from mga2 to not give unsecure browser to users?! If maintainer can't keep it up-to-date we have no good reasons to keep it :(
CC: (none) => sander.lepik
Hallo Here the same. An extension complains the outdated chromium version. It will stop working soon. Is there a chance to backport the version from cauldron? Thank you in advance!
CC: (none) => alfaflo
Feel free to update the chromium-browser-stable package
I wouldn't have asked if I could... :-) Not everyone who is interested in up to date software is a developer.
Packagers are not developers (some are but it's not an obligation)
new one, cauldron needs also an update
Summary: Update chromium to the last stable release : 16.0.912.63 to 17.0.963.46 => Update chromium to the last stable release : 16.0.912.63 to 18.0.1025.151
I think it would be easier to resolve this with removing it from repos and adding it to task-obsolete. We have no real maintainer for it. It's a shame but what can we do.
Blocks: (none) => 5046
i will update it and work to maintain it.
(In reply to comment #12) > i will update it and work to maintain it. For how long time? So that we get it into mga2 and it will fall out of updates again? Do we really need that? If mga2 is out you'll have to keep it up to date on caudron, on mga2 and on mga1. Do you promise that you have that time?
Blocks: 5046 => (none)
chromium-browser-stable-18.0.1025.168 has been uploaded into updates_testing. Testing on x86_64 completed. Seems to work fine. No regressions for me.
Hardware: i586 => AllAssignee: dmorganec => qa-bugs
Tested x86_64 too. Flash at youtube, java at http://www.java.com/en/download/testjava.jsp Imported from firefox. Added addons. Browsed https. Spellchecker is using correct language and is working. No problems here either.
Tested OK i586 Validating Advisory --------------- This updates Chromium browser to the latest stable version. --------------- SRPM: chromium-browser-stable-18.0.1025.168 Could sysadmin please push from core/updates_testing to core/updates Thanks!
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
Update pushed
Status: NEW => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED