Bug 5987

Summary:	Pre 2 Final - chromium-browser < 1:9.0.597.94 is obsoleted by (installed) chromium-browser-stable-18.0.1025.168-1.mga2.x86_64
Product:	Mageia	Reporter:	Manuel Hiebel <manuel.mageia>
Component:	RPM Packages	Assignee:	D Morgan <dmorganec>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	dmorganec, sysadmin-bugs, thierry.vignaud
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	MGA2TOO
Source RPM:	chromium-browser-stable	CVE:
Status comment:

Description Manuel Hiebel 2012-05-20 02:56:40 CEST

Description of problem:

After selecting all checkbox in the installer I get near to the end:

* 3 installation transactions failed
* chromium-browser < 1:9.0.597.94 is obsoleted by (installed) chromium-browser-stable-18.0.1025.168-1.mga2.x86_64

that come from the log, but I get the error in the windows/gui too

after the it seems to start fine.

(I will another bug for the other one
libgnome-media-profiles-3.0.so.0()(64bit) is needed by gnome-media-2.91.2-1.mga2.x86_64
x11-driver-video-fbdev is needed by x11-driver-video-1.0.0-37.mga2.x86_64
x11-driver-video-mga is needed by x11-driver-video-1.0.0-37.mga2.x86_64)

Comment 1 Manuel Hiebel 2012-05-20 02:58:03 CEST

or we can remove the package from the iso of courses...

Priority: Normal => release_blocker
CC: (none) => dmorganec, thierry.vignaud
Component: Release (media or process) => RPM Packages

Thierry Vignaud 2012-05-20 12:41:40 CEST

Assignee: bugsquad => dmorganec

Comment 2 Manuel Hiebel 2012-05-21 00:09:34 CEST

not sure but seems the package chromium-browser was removed (even if the -stable one is still there), so no errors anymore

Priority: release_blocker => Normal

Comment 3 Marja Van Waes 2012-05-26 13:03:53 CEST

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Manuel Hiebel 2012-05-26 17:33:33 CEST

Keywords: NEEDINFO => (none)
Whiteboard: (none) => MGA2TOO

Comment 4 Marja Van Waes 2012-07-06 15:05:06 CEST

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

Comment 5 D Morgan 2013-09-18 00:03:17 CEST

is this fixed in cauldron ?

Comment 6 Manuel Hiebel 2013-09-18 11:42:14 CEST

I would say no

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