3:20 p.m.
Just noticed that the current chromium in epel-testing can not be
installed on E9 with rpmfusion repo enabled. All versions before did not
have this problem. It seems the build pulls a new dep (libavformat-free)
that conflicts with ffmpeg-libs of rpmfusion. This results in an
incompatibility with rpmfusion repos. Is this intentional?
--
Leon
7:30 a.m.
On Sat, Nov 18, 2023 at 4:20 PM Leon Fauster via epel-devel
<epel-devel(a)lists.fedoraproject.org> wrote:
Just noticed that the current chromium in epel-testing can not be
installed on E9 with rpmfusion repo enabled. All versions before did not
have this problem. It seems the build pulls a new dep (libavformat-free)
that conflicts with ffmpeg-libs of rpmfusion. This results in an
incompatibility with rpmfusion repos. Is this intentional?
Yes. If you want expanded codec support, install the
libavcodec-freeworld overlay package instead.
--
真実はいつも一つ！/ Always, there's only one truth!
4:25 p.m.
Am 19.11.23 um 14:30 schrieb Neal Gompa:
On Sat, Nov 18, 2023 at 4:20 PM Leon Fauster via epel-devel
<epel-devel(a)lists.fedoraproject.org> wrote:
>
> Just noticed that the current chromium in epel-testing can not be
> installed on E9 with rpmfusion repo enabled. All versions before did not
> have this problem. It seems the build pulls a new dep (libavformat-free)
> that conflicts with ffmpeg-libs of rpmfusion. This results in an
> incompatibility with rpmfusion repos. Is this intentional?
>
Yes. If you want expanded codec support, install the
libavcodec-freeworld overlay package instead.
Not sure what scenario is supported now. A common
workstation setup has rpmfusion applications installed
(ffmpeg, mpv, libavcodec-freeworld). Do I understand
it correctly that I must remove ffmpeg-libs to install
chromium now?
Not sure if the new spec design with "Conflicts: ffmpeg-libs"
has more a fedora context in mind. As both packages
libavcodec-free and ffmpeg-libs provide the needed lib.
[root@ss ~]# LANG=C yum update --enablerepo=epel-testing
Last metadata expiration check: 0:24:05 ago on Sun Nov 19 22:43:58 2023.
Dependencies resolved.
Problem 1: package chromium-119.0.6045.159-1.el9.x86_64 conflicts with
ffmpeg-libs(x86-64) provided by ffmpeg-libs-5.1.3-1.el9.x86_64
- cannot install the best update candidate for package
ffmpeg-libs-5.1.3-1.el9.x86_64
- cannot install the best update candidate for package
chromium-119.0.6045.123-1.el9.x86_64
Problem 2: package libavdevice-5.1.3-1.el9.x86_64 requires
ffmpeg-libs(x86-64) = 5.1.3-1.el9, but none of the providers can be
installed
- package chromium-119.0.6045.159-1.el9.x86_64 conflicts with
ffmpeg-libs(x86-64) provided by ffmpeg-libs-5.1.3-1.el9.x86_64
- problem with installed package chromium-119.0.6045.123-1.el9.x86_64
- package chromium-119.0.6045.123-1.el9.x86_64 requires
chromium-common(x86-64) = 119.0.6045.123-1.el9, but none of the
providers can be installed
- cannot install both chromium-common-119.0.6045.159-1.el9.x86_64 and
chromium-common-119.0.6045.123-1.el9.x86_64
- cannot install the best update candidate for package
libavdevice-5.1.3-1.el9.x86_64
- cannot install the best update candidate for package
chromium-common-119.0.6045.123-1.el9.x86_64
=============================================================================================================================================================================
Package Architecture Version
Repository
Size
=============================================================================================================================================================================
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
chromium x86_64
119.0.6045.159-1.el9 epel-testing
81 M
chromium-common x86_64
119.0.6045.159-1.el9 epel-testing
13 M
Transaction Summary
=============================================================================================================================================================================
Skip 2 Packages
Nothing to do.
Complete!
[root@ss ~]#
--
Leon
6:38 p.m.
On Sun, Nov 19, 2023 at 5:25 PM Leon Fauster via epel-devel
<epel-devel(a)lists.fedoraproject.org> wrote:
Am 19.11.23 um 14:30 schrieb Neal Gompa:
> On Sat, Nov 18, 2023 at 4:20 PM Leon Fauster via epel-devel
> <epel-devel(a)lists.fedoraproject.org> wrote:
>>
>> Just noticed that the current chromium in epel-testing can not be
>> installed on E9 with rpmfusion repo enabled. All versions before did not
>> have this problem. It seems the build pulls a new dep (libavformat-free)
>> that conflicts with ffmpeg-libs of rpmfusion. This results in an
>> incompatibility with rpmfusion repos. Is this intentional?
>>
>
> Yes. If you want expanded codec support, install the
> libavcodec-freeworld overlay package instead.
>
>
Not sure what scenario is supported now. A common
workstation setup has rpmfusion applications installed
(ffmpeg, mpv, libavcodec-freeworld). Do I understand
it correctly that I must remove ffmpeg-libs to install
chromium now?
Not sure if the new spec design with "Conflicts: ffmpeg-libs"
has more a fedora context in mind. As both packages
libavcodec-free and ffmpeg-libs provide the needed lib.
Strictly speaking, from a Fedora context, RPM Fusion is not supported
beyond limited cases. That said, EPEL has mpv itself too.
The "recommended" (as far as recommendations go when it comes to third
party repositories) path is to use Fedora's ffmpeg-free stack and then
install libavcodec-freeworld on top if there are codecs you are
missing that you need. That package overlays a libavcodec build that
includes things Fedora cannot ship at this time.
--
真実はいつも一つ！/ Always, there's only one truth!
2:42 p.m.
Am 20.11.23 um 01:38 schrieb Neal Gompa:
On Sun, Nov 19, 2023 at 5:25 PM Leon Fauster via epel-devel
<epel-devel(a)lists.fedoraproject.org> wrote:
>
> Am 19.11.23 um 14:30 schrieb Neal Gompa:
>> On Sat, Nov 18, 2023 at 4:20 PM Leon Fauster via epel-devel
>> <epel-devel(a)lists.fedoraproject.org> wrote:
>>>
>>> Just noticed that the current chromium in epel-testing can not be
>>> installed on E9 with rpmfusion repo enabled. All versions before did not
>>> have this problem. It seems the build pulls a new dep (libavformat-free)
>>> that conflicts with ffmpeg-libs of rpmfusion. This results in an
>>> incompatibility with rpmfusion repos. Is this intentional?
>>>
>>
>> Yes. If you want expanded codec support, install the
>> libavcodec-freeworld overlay package instead.
>>
>>
>
>
>
>
> Not sure what scenario is supported now. A common
> workstation setup has rpmfusion applications installed
> (ffmpeg, mpv, libavcodec-freeworld). Do I understand
> it correctly that I must remove ffmpeg-libs to install
> chromium now?
> Not sure if the new spec design with "Conflicts: ffmpeg-libs"
> has more a fedora context in mind. As both packages
> libavcodec-free and ffmpeg-libs provide the needed lib.
>
>
Strictly speaking, from a Fedora context, RPM Fusion is not supported
beyond limited cases. That said, EPEL has mpv itself too.
The "recommended" (as far as recommendations go when it comes to third
party repositories) path is to use Fedora's ffmpeg-free stack and then
install libavcodec-freeworld on top if there are codecs you are
missing that you need. That package overlays a libavcodec build that
includes things Fedora cannot ship at this time.
Thanks Neal for the overview.
The specific issue was addressed now.
https://src.fedoraproject.org/rpms/chromium/c/cfac4f7e0f0cae0daffbbad5c4c...
Lets see when its in the repo.
--
Leon
5:51 a.m.
Am 20.11.23 um 21:42 schrieb Leon Fauster:
Am 20.11.23 um 01:38 schrieb Neal Gompa:
> On Sun, Nov 19, 2023 at 5:25 PM Leon Fauster via epel-devel
> <epel-devel(a)lists.fedoraproject.org> wrote:
>>
>> Am 19.11.23 um 14:30 schrieb Neal Gompa:
>>> On Sat, Nov 18, 2023 at 4:20 PM Leon Fauster via epel-devel
>>> <epel-devel(a)lists.fedoraproject.org> wrote:
>>>>
>>>> Just noticed that the current chromium in epel-testing can not be
>>>> installed on E9 with rpmfusion repo enabled. All versions before
>>>> did not
>>>> have this problem. It seems the build pulls a new dep
>>>> (libavformat-free)
>>>> that conflicts with ffmpeg-libs of rpmfusion. This results in an
>>>> incompatibility with rpmfusion repos. Is this intentional?
>>>>
>>>
>>> Yes. If you want expanded codec support, install the
>>> libavcodec-freeworld overlay package instead.
>>>
>>>
>>
>>
>>
>>
>> Not sure what scenario is supported now. A common
>> workstation setup has rpmfusion applications installed
>> (ffmpeg, mpv, libavcodec-freeworld). Do I understand
>> it correctly that I must remove ffmpeg-libs to install
>> chromium now?
>> Not sure if the new spec design with "Conflicts: ffmpeg-libs"
>> has more a fedora context in mind. As both packages
>> libavcodec-free and ffmpeg-libs provide the needed lib.
>>
>>
>
> Strictly speaking, from a Fedora context, RPM Fusion is not supported
> beyond limited cases. That said, EPEL has mpv itself too.
>
> The "recommended" (as far as recommendations go when it comes to third
> party repositories) path is to use Fedora's ffmpeg-free stack and then
> install libavcodec-freeworld on top if there are codecs you are
> missing that you need. That package overlays a libavcodec build that
> includes things Fedora cannot ship at this time.
>
Thanks Neal for the overview.
The specific issue was addressed now.
https://src.fedoraproject.org/rpms/chromium/c/cfac4f7e0f0cae0daffbbad5c4c...
Lets see when its in the repo.
JFI - rpmfusion's packages can coexists now. With the full-fledged
ffmpeg of rpmfusion the libavcodec-freeworld package is not needed.
Thanks to @than the packager!
# LANG=C yum update --enablerepo=epel-testing
--enablerepo=rpmfusion-free-updates-testing chromium
Last metadata expiration check: 0:04:06 ago on Tue Nov 21 12:40:55 2023.
Dependencies resolved.
=======================================================================
Package Architecture
Version Repository
Size
=======================================================================
Upgrading:
chromium x86_64
119.0.6045.159-2.el9 epel-testing
81 M
chromium-common x86_64
119.0.6045.159-2.el9 epel-testing
13 M
ffmpeg x86_64
5.1.4-1.el9
rpmfusion-free-updates-testing 1.7 M
ffmpeg-libs x86_64
5.1.4-1.el9
rpmfusion-free-updates-testing 7.8 M
libavdevice x86_64
5.1.4-1.el9
rpmfusion-free-updates-testing 72 k
Transaction Summary
=======================================================================
Upgrade 5 Packages
--
Leon
4:07 p.m.
Le lun. 20 nov. 2023 à 01:38, Neal Gompa <ngompa13(a)gmail.com> a écrit :
On Sun, Nov 19, 2023 at 5:25 PM Leon Fauster via epel-devel
<epel-devel(a)lists.fedoraproject.org> wrote:
>
> Am 19.11.23 um 14:30 schrieb Neal Gompa:
> > On Sat, Nov 18, 2023 at 4:20 PM Leon Fauster via epel-devel
> > <epel-devel(a)lists.fedoraproject.org> wrote:
> >>
> >> Just noticed that the current chromium in epel-testing can not be
> >> installed on E9 with rpmfusion repo enabled. All versions before did not
> >> have this problem. It seems the build pulls a new dep (libavformat-free)
> >> that conflicts with ffmpeg-libs of rpmfusion. This results in an
> >> incompatibility with rpmfusion repos. Is this intentional?
> >>
> >
> > Yes. If you want expanded codec support, install the
> > libavcodec-freeworld overlay package instead.
> >
> >
>
>
>
>
> Not sure what scenario is supported now. A common
> workstation setup has rpmfusion applications installed
> (ffmpeg, mpv, libavcodec-freeworld). Do I understand
> it correctly that I must remove ffmpeg-libs to install
> chromium now?
> Not sure if the new spec design with "Conflicts: ffmpeg-libs"
> has more a fedora context in mind. As both packages
> libavcodec-free and ffmpeg-libs provide the needed lib.
>
>
Strictly speaking, from a Fedora context, RPM Fusion is not supported
beyond limited cases. That said, EPEL has mpv itself too.
@Neal
Can you clarify why you Conflicts about ffmpeg-libs from rpmfusion
whereas we have fixed the incompatibilities ?
Please don't push breaking packages without the needed coordination
notice, people aren't necessarily able to react at your own pace and
this is perceived as tremendously aggressive !
@Adrew, there is a rpmfusion-free-updates-testing ffmpeg package that
is compatible with the chromium newer releases. (for epel9)
It will be pushed to stable ASAP.
2:08 a.m.
On Sat, 18 Nov 2023, Leon Fauster via epel-devel wrote:
Just noticed that the current chromium in epel-testing can not be
installed
on E9 with rpmfusion repo enabled. All versions before did not have this
problem. It seems the build pulls a new dep (libavformat-free) that conflicts
with ffmpeg-libs of rpmfusion. This results in an incompatibility with
rpmfusion repos. Is this intentional?
From a recent post to this list:
Date: Sat, 18 Nov 2023 02:01:08 +0000 (UTC)
From: updates(a)fedoraproject.org
Reply-To: EPEL Development List <epel-devel(a)lists.fedoraproject.org>
To: epel-devel(a)lists.fedoraproject.org
Subject: [EPEL-devel] Fedora EPEL 9 updates-testing report
... ... ...
==============================================================================
chromium-119.0.6045.159-1.el9 (FEDORA-EPEL-2023-03f6b44faf)
A WebKit (Blink) powered web browser that Google doesn't want you to use
--------------------------------------------------------------------------------
Update Information:
... ... ...
ChangeLog:
* Wed Nov 15 2023 Than Ngo <than(a)redhat.com> - 119.0.6045.159-1
- update to 119.0.6045.159, upstream security release
High CVE-2023-5997, use after free in Garbage Collection
High CVE-2023-6112, use after free in Navigation
- add Requires/Conflicts for ABI break in fmpeg-free 6.0.1
...
... ...
So it does look like an intentional, but needed, incompatability :-(
--
Andrew C. Aitchison Kendal, UK
andrew(a)aitchison.me.uk
180
days inactive
183
days old
epel-devel@lists.fedoraproject.org
7 comments
4 participants
participants (4)
-
Andrew C Aitchison -
Leon Fauster -
Neal Gompa -
Nicolas Chauvet