I am trying to install this on Centos 8 and get the following error using sudo dnf install chromium --enablerepo=epel-testing --refresh
:
Error:
Problem: conflicting requests
- nothing provides nss-mdns(x86-64) needed by chromium-77.0.3865.90-3.el8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
I have the following repos enables:
AppStream CentOS-8 - AppStream 4,928
BaseOS CentOS-8 - Base 2,713
PowerTools CentOS-8 - PowerTools 1,473
brave-browser-rpm-release.s3.brave.com_x86_64_ created by dnf config-manager from https://brave-browser-rpm-release.s3.brave.com/x86_64/ 25
code Visual Studio Code 70
*epel Extra Packages for Enterprise Linux 8 - x86_64 1,846
extras CentOS-8 - Extras 3
rpmfusion-free-updates RPM Fusion for EL 8 - Free - Updates 115
rpmfusion-nonfree-updates
I can add these using Brave on Centos 8, so I assume this is a problem with the Chromium build.
(on a side note, I only just got a Fedora account and can't seem to edit my previous entry and karma vote, so sorry if I made an error and am making multiple posts for nothing)
This update can be pushed to stable now if the maintainer wishes
sumomo, your bug is legitimate, but I don't think it is in chromium, but rather, minizip. I can reproduce this, but only on EL8, and the build is identical to Fedora here. This bug is also present in the chromium 78 epel8 build I just tested. Debugging this is rather confusing, since it dies after mz_stream_create.
I opened a bug against minizip on this (before the bugzilla server went on maintenance this morning).
I am pushing this to stable.
The browser is working correctly. There is possibly a bug, but I don't feel it is big enough to deny everyone else the browser based on a chrome web-store app.
There are also other EPEL8 packages that need nss-mdns.
This update has been submitted for stable by tdawson.
This update has been submitted for testing by spot.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
I am trying to install this on Centos 8 and get the following error using
sudo dnf install chromium --enablerepo=epel-testing --refresh
:I have the following repos enables:
Thanks.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
spot edited this update.
New build(s):
Karma has been reset.
This update has been submitted for testing by spot.
This update has been pushed to testing.
Thanks, works great on Centos 8 now.
After more testing I tried to install extensions from the chrome web store and got:
https://chrome.google.com/webstore/search/https%20everywhere https://chrome.google.com/webstore/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm?hl=en
I can add these using Brave on Centos 8, so I assume this is a problem with the Chromium build.
(on a side note, I only just got a Fedora account and can't seem to edit my previous entry and karma vote, so sorry if I made an error and am making multiple posts for nothing)
This update can be pushed to stable now if the maintainer wishes
sumomo, your bug is legitimate, but I don't think it is in chromium, but rather, minizip. I can reproduce this, but only on EL8, and the build is identical to Fedora here. This bug is also present in the chromium 78 epel8 build I just tested. Debugging this is rather confusing, since it dies after mz_stream_create.
I opened a bug against minizip on this (before the bugzilla server went on maintenance this morning).
Installs and works correctly.
I am pushing this to stable. The browser is working correctly. There is possibly a bug, but I don't feel it is big enough to deny everyone else the browser based on a chrome web-store app. There are also other EPEL8 packages that need nss-mdns.
This update has been submitted for stable by tdawson.
That's fine. The latest 78 build has the chrome store bug fixed.
This update has been pushed to stable.
This version is working well in Centos 8 (apart from the mentioned bug). Look forward to the next fully working 78 version.