Bug 22806 - Chromium cant be installed because of missing VPX4
Summary: Chromium cant be installed because of missing VPX4
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:
Depends on:
Blocks:
 
Reported: 2018-03-19 20:29 CET by Juan Magallon
Modified: 2018-07-05 23:55 CEST (History)
3 users (show)

See Also:
Source RPM: chromium-browser-stable-63.0.3239.108-1.mga7.src.rpm
CVE:
Status comment:

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

Description Juan Magallon 2018-03-19 20:29:16 CET 
On a fresh installed Cauldron, chromium can't be installed:
tmate:~# urpmi chromium-browser-stable
A requested package cannot be installed:
chromium-browser-stable-63.0.3239.108-1.mga7.x86_64 (due to unsatisfied libvpx.so.4()(64bit))
Continue installation anyway? (Y/n) 
While some packages may have been installed, there were failures.
A requested package cannot be installed:
chromium-browser-stable-63.0.3239.108-1.mga7.x86_64 (due to unsatisfied libvpx.so.4()(64bit))
Continue installation anyway?

lib64vpx4 is no more in repos, lib64vpx5 replaced it but Chromium is
missing a rebuild.
Comment 1 Stig-Ørjan Smelror 2018-03-19 23:43:21 CET 
As far as I know, Chromium is having trouble building because it times out and dies. I guess that's why the "old" version won't install.

Cheers,
Stig

CC: (none) => smelror

Comment 2 Marja Van Waes 2018-03-20 13:17:04 CET 
Assigning to the registered maintainer.

CC: (none) => marja11
Assignee: bugsquad => cjw

Comment 3 Jeremiah Summers 2018-04-11 01:24:50 CEST 
There's quite a few packages that relied on libvpx.so.4, that now have broken deps. Shall I create a new ticket with a list of those?

CC: (none) => JMiahMan

Comment 4 Christiaan Welvaart 2018-07-05 23:55:28 CEST 
Build timeout was increased for all packages.

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.