Bug 27086 - chromium-browser-stable needs rebuilt (and updated) in Cauldron
Summary: chromium-browser-stable needs rebuilt (and updated) in Cauldron
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Christiaan Welvaart
QA Contact:
URL:
Whiteboard:
Keywords:
: 27067 27157 27583 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-08-12 04:01 CEST by William Kenney
Modified: 2020-11-18 16:06 CET (History)
4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description William Kenney 2020-08-12 04:01:26 CEST 
Description of problem:


Attemps to install the Chrome Browser from the MCC result in an error:

Sorry, the following package cannot be selected:

- chromium-browser-stable-81.0.4044.138-1.mga8.x86_64 (due to unsatisfied libicuuc.so.66()(64bit))
Comment 1 David Walser 2020-08-12 17:03:22 CEST 
Chromium is not Chrome.  It just hasn't been updated since the icu update.  See also Bug 26648.

Source RPM: chrome => chromium-browser-stable
Summary: Attemps to install the Chrome Browser from the MCC result in an error => chromium-browser-stable needs rebuilt (and updated) in Cauldron
Assignee: bugsquad => cjw

Comment 2 David Walser 2020-08-22 00:00:14 CEST 
*** Bug 27157 has been marked as a duplicate of this bug. ***

CC: (none) => joselp

Stéphane Pontier 2020-08-23 14:11:36 CEST

CC: (none) => stephane.pontier

Comment 3 Aurelien Oudelet 2020-11-09 11:56:43 CET 
*** Bug 27583 has been marked as a duplicate of this bug. ***

CC: (none) => heninj

Comment 4 David Walser 2020-11-18 15:12:42 CET 
*** Bug 27067 has been marked as a duplicate of this bug. ***

CC: (none) => jeanmichel.varvou

Comment 5 David Walser 2020-11-18 15:13:08 CET 
Package removed from Cauldron.

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

Comment 6 Jérôme Hénin 2020-11-18 16:06:07 CET 
Since this is an unusual fix, can we please have a little context? Is that final, ie. giving up on the package entirely, or temporary, eg. waiting for something to change upstream?

I'm not trying to criticize the process, just to understand it. Thanks!
Note You need to log in before you can comment on or make changes to this bug.