Hello Troy,

thank you for mentioning epel next. To be fair the name is quite confusing, I would not have thought this was supposed to be for CentOS 8 Stream to be fair. It might be a good idea to rename it to epel-stream maybe.

Anyway unfortunately it doesn't look like it's solving the issue

[root@f462d-15562d ~]# dnf update
Extra Packages for Enterprise Linux 8 - Next - x86_64                                                                                                       1.3 MB/s | 1.2 MB     00:00
Last metadata expiration check: 0:00:01 ago on Fri 20 Aug 2021 17:00:50 CEST.
Error:
 Problem: package xorgxrdp-0.2.16-2.el8.x86_64 requires xorg-x11-server-Xorg(x86-64) = 1.20.10, but none of the providers can be installed
  - cannot install both xorg-x11-server-Xorg-1.20.11-2.el8.x86_64 and xorg-x11-server-Xorg-1.20.10-1.el8.x86_64
  - cannot install the best update candidate for package xorgxrdp-0.2.16-2.el8.x86_64
  - cannot install the best update candidate for package xorg-x11-server-Xorg-1.20.10-1.el8.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Let me also mention that the xorgxrdp maintainer in EPEL mentioned (see the bug report) that "xorg-x11-server-Xorg-1.20.11-2.el8 in Fedora's koji yet", so he is unable to build the package.

So it seems that, despite epel-next exists either this maintainer doesn't know how to use it or there is an infrastructure problem. I'll ask in the bug report.

Kind regards.

Enrico Tagliavini

On Fri, Aug 20, 2021 at 4:42 PM Troy Dawson <tdawson@redhat.com> wrote:


On Fri, Aug 20, 2021 at 7:08 AM Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
Hello folks,

I've just noticed that some packages in EPEL 8 are broken when used in CentOS 8 Stream. One example:


which has been broken for a long time now (from well before I decided to finally report the bug).

EPEL 8 is fundamental for me, I can't use the system without. So here is the important question: is the EPEL project going to support CentOS 8 Stream?

With CentOS 8 gone I didn't mind to switch to CentOS 8 Stream, I thought that for my use it would be ok... until I noticed packages in EPEL 8 not working.

It's very important for me to know the answer to this as if the answer is no I have to drop CentOS 8 Stream right away and switch to something else, like RockyLinux or Alma.

Thank you.
Kind regards.

Enrico Tagliavini

Hi Enrico,
epel has epel-next that is compatible with CentOS Stream.
https://fedoraproject.org/wiki/EPEL_Next

epel-next is layered on top of regular epel.  It is meant to only have those packages that need to be rebuilt for CentOS Stream.  This is because over 90% of epel packages "just work" on CentOS Stream.

If you have epel installed, you should also have epel-next-release installed.  It should have happened automatically, but if it didn't, you can do a
  dnf install epel-next-release

All that being said, you did the correct thing in opening a bug.  It's possible the package maintainer doesn't know that the package needs to be updated.

Although we are working on something automatic that will alert the maintainers when their packages are no longer installable in CentOS Stream, that is currently lower in priority to getting epel9-next out.  Since EPEL is 100% volunteer driven, some things take more time to implement.

Again, thank you for the bug, it helps.
Troy Dawson




_______________________________________________
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-leave@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.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure