Il giorno gio 21 set 2023 alle ore 16:38 Eric Curtin <ecurtin@redhat.com> ha scritto:

Another similar technique that's also helpful, is if we ask the Fedora
maintainer to create an EPEL9 version of the package, that way the
community can help maintain the package and you can just "mirror" EPEL
(assuming you keep an eye on the changes they make).

I did this recently when I asked the erofs-utils maintainer to create
an EPEL9 rpm for our erosfs related features we are working on:

https://src.fedoraproject.org/rpms/erofs-utils

I'm not sure this is a good idea.

According to https://www.redhat.com/en/blog/whats-epel-and-how-do-i-use-it

```

EPEL is a selection of packages from Fedora, but only packages that are not in RHEL or its layered products to avoid conflicts.

```

And RHIVOS is a layered product so having stuff in EPEL may end up with conflicts later on.

We had similar issues with mom and vdsm packages which were also shipped in Red Hat Virtualization (downstream of oVirt project) in the past and we had to drop them from EPEL to solve issues.

I would rather avoid AutoSD collisions with EPEL if possible.

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING

Red Hat In-Vehicle Operating System

Red Hat EMEA

Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.