The maintainer knows and is working on it.
https://bugzilla.redhat.com/show_bug.cgi?id=1825510#c10
https://src.fedoraproject.org/rpms/chromium/c/fe113522cb8874a57e326527262...
(same commit in epel7, epel8, and f32)
On Mon, Apr 20, 2020 at 3:36 PM Leon Fauster <leonfauster(a)googlemail.com> wrote:
Am 20.04.20 um 22:27 schrieb updates(a)fedoraproject.org:
> The following Fedora EPEL 8 Security updates need testing:
> Age URL
> 12
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-8fcf741d7f
cacti-1.2.11-1.el8 cacti-spine-1.2.11-1.el8
> 2
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-dfc01a6be3
chromium-81.0.4044.113-1.el8
> 0
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-5af12f8767
ansible-2.9.7-1.el8
>
JFYI: I installed (updated) chromium from epel-testing today. What I
noticed was that chromium-common package was not pulled at the same
time while updating (yum update --enablerepo=epel-testing chromium).
At the end I had a chromium-81 and a chromium-common-80 package installed.
Maybe adding something like
Requires: chromium-common = %{version}-%{release}
into the chromium.spec file resolves this?
--
Leon
_______________________________________________
epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org
To unsubscribe send an email to epel-devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproj...
--
Carl George