# EPEL broken... now what?

**URL:** https://forums.rockylinux.org/t/epel-broken-now-what/13887
**Category:** Rocky Linux Help & Support
**Created:** [May 5, 2024, 3:28pm UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887 "2024-05-05T15:28:59Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![microlinux](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/microlinux/32/1244_2.png) [@microlinux](https://forums.rockylinux.org/u/microlinux)
#### Post date: [May 5, 2024, 3:28pm UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/1 "2024-05-05T15:28:59Z")

</div>

Hi,

Here’s what I get when I try to update a box running Rocky Linux 9 with KDE from EPEL:

```auto
# dnf update
Error: 
 Problem: cannot install the best update candidate for package kf5-libkdcraw-23.04.3-2.el9.x86_64
  - nothing provides libraw.so.23()(64bit) needed by kf5-libkdcraw-23.08.5-1.el9.x86_64 from epel
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

```

Now I know this is due to Red Hat having published RHEL 9.4 and EPEL following closely.

Any advice on how to handle this? Is there some timeline to address to resolve this kind of issue?

Cheers,

Niki

---

<div class="post-metadata">

### Author: ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)
#### Post date: [May 5, 2024, 3:46pm UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/2 "2024-05-05T15:46:41Z")

</div>

Suggest waiting until Rocky 9.4 is released. This is unfortunately what happens when there is a new RHEL release that EPEL follows. Nothing you can do until Rocky 9.4 is released.

---

<div class="post-metadata">

### Author: ![microlinux](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/microlinux/32/1244_2.png) [@microlinux](https://forums.rockylinux.org/u/microlinux)
#### Post date: [May 5, 2024, 4:08pm UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/3 "2024-05-05T16:08:43Z")

</div>

Just curious : is this a matter of days ? Or more like weeks ? I know the maintainers are already doing some great work. Just wanted to know what to expect.

---

<div class="post-metadata">

### Author: ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)
#### Post date: [May 5, 2024, 4:22pm UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/4 "2024-05-05T16:22:54Z")

</div>

Testing is in progress, of ISO’s, etc, so I expect days max.

---

<div class="post-metadata">

### Author: ![JustSomeone](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@JustSomeone](https://forums.rockylinux.org/u/JustSomeone)
#### Post date: [May 5, 2024, 4:29pm UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/5 "2024-05-05T16:29:11Z")

</div>

you can peek on the stg repo it has the pre release

[https://download.rockylinux.org/stg/rocky/](https://download.rockylinux.org/stg/rocky/)

they just released the rc1 of 9.4

and have a nice day everyone 🙂

---

<div class="post-metadata">

### Author: ![ganphx](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/ganphx/32/2381_2.png) [@ganphx](https://forums.rockylinux.org/u/ganphx)
#### Post date: [May 5, 2024, 4:56pm UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/6 "2024-05-05T16:56:04Z")

</div>

Looks like the new LibRaw requires rebuilding some epel packages for 9.4.

[https://bugzilla.redhat.com/buglist.cgi?bug\_status=\_\_all\_\_&content=libraw&no\_redirect=1&order=Importance&query\_format=specific](https://bugzilla.redhat.com/buglist.cgi?bug_status= __all__ &content=libraw&no_redirect=1&order=Importance&query_format=specific)

---

<div class="post-metadata">

### Author: ![phyzical](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/phyzical/32/2972_2.png) [@phyzical](https://forums.rockylinux.org/u/phyzical)
#### Post date: [May 8, 2024, 2:46am UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/7 "2024-05-08T02:46:40Z")

</div>

out of curiosity, how does the REHL update cause epel to start refusing to provide packages even though epel itself hasn’t updated?

Just trying to workout if there’s something we can do in our build pipeline to avoid this sort of issue in the future as it is currently blocking us from building docker containers .

Edit: my interim workaround is to just install the centos version

```auto
 yum -y install \
    # renovate: datasource=yum repo=rocky-9-extras-x86_64
    epel-release-9-7.el9 \
    # TODO: Remove this once 9.4 is out
    https://mirror.stream.centos.org/9-stream/AppStream/${ARCH}/os/Packages/LibRaw-0.21.1-1.el9.${ARCH}.rpm \

```

---

<div class="post-metadata">

### Author: ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)
#### Post date: [May 8, 2024, 5:37am UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/8 "2024-05-08T05:37:55Z")

</div>

> [@phyzical](#):
>
> out of curiosity, how does the REHL update cause epel to start refusing to provide packages even though epel itself hasn’t updated?

EPEL packages certain software and libraries that hook into dependencies that are in EL. These dependencies may have a specific ABI. Once that ABI changes, everything that relies on it must be rebuilt. For example, EPEL provides KDE Plasma packages. If qt5 packages update in EL, just about _everything_ related to KDE in EPEL must be rebuilt. There’s no getting around this.

What sometimes happens is some packages may get rebuilt in EPEL when RHEL is released. Rebuilds/derivatives (like Rocky Linux) don’t release on the same day as RHEL, so folks who may be using KDE for example will fail to update their systems until we release a new package.

Until Rocky Linux 9.4 comes out, there’s nothing more that can be done.

---

<div class="post-metadata">

### Author: ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)
#### Post date: [May 8, 2024, 5:57am UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/9 "2024-05-08T05:57:51Z")

</div>

I’d add to that that EPEL is not “one”, unlike RHEL and Rocky.  
There was a moment, when all packages of RHEL 9.4 became available.  
There will be a moment, when all packages of Rocky 9.4 become available.

EPEL is not “all at once”, but a community of maintainers. All (new) packages  
are not released simultaneously. They come when/if they get (re)built (and tested).

---

<div class="post-metadata">

### Author: ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)
#### Post date: [May 8, 2024, 6:07am UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/10 "2024-05-08T06:07:35Z")

</div>

> [@jlehtone](#):
>
> EPEL is not “all at once”, but a community of maintainers. All (new) packages  
> are not released simultaneously. They come when/if they get (re)built (and tested).

You seem to be focusing on the present and not the historical context because that is not how it was historically. This means very recently maintainers and EPEL sig leaders have actually decided to think about the derivatives rather than just RHEL. It is only a recent occurrence that somethings ( **not all** ) are held back until the other derivatives are ready. Yes, it remains at maintainer’s discretion.

Note that 10 will be much cleaner/easier in this regard as they will maintain 10.X directories, with 10.X+1 in development and made “stable” once a minor release is available.

---

<div class="post-metadata">

### Author: ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)
#### Post date: [May 8, 2024, 6:15am UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/11 "2024-05-08T06:15:24Z")

</div>

The present affects today, doesn’t it?

> [@label](#):
>
> Note that 10 will be much cleaner/easier in this regard as they will maintain 10.X directories, with 10.X+1 in development and made “stable” once a minor release is available.

Awesome.

---

<div class="post-metadata">

### Author: ![ganphx](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/ganphx/32/2381_2.png) [@ganphx](https://forums.rockylinux.org/u/ganphx)
#### Post date: [May 8, 2024, 4:18pm UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/12 "2024-05-08T16:18:52Z")

</div>

The full discussion for the EPEL 10 proposal is listed here.

[https://discussion.fedoraproject.org/t/epel-10-proposal/44304](https://discussion.fedoraproject.org/t/epel-10-proposal/44304)

---

<div class="post-metadata">

### Author: ![kiltedknight](https://avatars.discourse-cdn.com/v4/letter/k/ecae2f/32.png) [@kiltedknight](https://forums.rockylinux.org/u/kiltedknight)
#### Post date: [May 9, 2024, 7:49pm UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/13 "2024-05-09T19:49:34Z")

</div>

I submitted a bug to the Red Hat/Fedora Bugzilla, and they told me that it’s because Rocky tracks RHEL 9.3 at the moment… so being an adventurous systems engineer, I went and found the Alma 9.4 srpm, downloaded it, built it, and installed it. No complaints along the way when I did.

---

<div class="post-metadata">

### Author: ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)
#### Post date: [May 9, 2024, 8:34pm UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/14 "2024-05-09T20:34:25Z")

</div>

> [@kiltedknight](#):
>
> I went and found the Alma 9.4 srpm, downloaded it, built it, and installed it. No complaints along the way when I did.

Not a good idea, since Alma doesn’t track RHEL anymore. You’ve just compiled and installed something that now means your system has diverged from Rocky. You should have just waited until Rocky releases 9.4 shortly.

---

<div class="post-metadata">

### Author: ![kiltedknight](https://avatars.discourse-cdn.com/v4/letter/k/ecae2f/32.png) [@kiltedknight](https://forums.rockylinux.org/u/kiltedknight)
#### Post date: [May 9, 2024, 9:02pm UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/15 "2024-05-09T21:02:12Z")

</div>

CentOS 9 Stream has the same one… LibRaw-0.21.1-1.el9.src.rpm

---

<div class="post-metadata">

### Author: ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)
#### Post date: [May 9, 2024, 9:04pm UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/16 "2024-05-09T21:04:23Z")

</div>

Even worse, since stream also isn’t Rocky Linux, so doing what you have done is a bad idea. Rocky 9.4 will be released shortly, so it’s just silly doing such things like that.

---

<div class="post-metadata">

### Author: ![FloppyDisk](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/floppydisk/32/4256_2.png) [@FloppyDisk](https://forums.rockylinux.org/u/FloppyDisk)
#### Post date: [May 9, 2024, 10:57pm UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/17 "2024-05-09T22:57:34Z")

</div>

You can just replace $releasever with 9.3 in

```auto
sed -i 's/\$releasever/9.3/g' /etc/yum.repos.d/rocky.repo
sed -i 's/\$releasever/9.3/g' /etc/yum.repos.d/rocky-extras.repo

```

then revert it later on

```auto

sed -i 's/9.3/\$releasever/g' /etc/yum.repos.d/rocky.repo
sed -i 's/9.3/\$releasever/g' /etc/yum.repos.d/rocky-extras.repo

```

---

<div class="post-metadata">

### Author: ![willnode](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/willnode/32/4257_2.png) [@willnode](https://forums.rockylinux.org/u/willnode)
#### Post date: [May 9, 2024, 11:17pm UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/18 "2024-05-09T23:17:10Z")

</div>

Thank you! I need quick fix right now and this worked smoothly.

---

<div class="post-metadata">

### Author: ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)
#### Post date: [May 10, 2024, 9:11am UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/19 "2024-05-10T09:11:26Z")

</div>

> [@Rocky Linux 9.4 Available Now](https://forums.rockylinux.org/t/rocky-linux-9-4-available-now/13978):
>
> Rocky Linux 9.4 has been released. See our [release announcement](https://rockylinux.org/news/rocky-linux-9-4-ga-release) for more details. Thank you for supporting Rocky Linux! Sincerely, Release Engineering @ The Rocky Linux Project [https://rockylinux.org](https://rockylinux.org)

---

<div class="post-metadata">

### Author: ![markidx](https://avatars.discourse-cdn.com/v4/letter/m/54ee81/32.png) [@markidx](https://forums.rockylinux.org/u/markidx)
#### Post date: [May 19, 2024, 6:41pm UTC](https://forums.rockylinux.org/t/epel-broken-now-what/13887/20 "2024-05-19T18:41:10Z")

</div>

I am uncertain what to think…I just downloaded and created a workstation with 9.4 DVD yet the problem is still there. Have I done something wrong? I cannot install anything, even after a yum update to ensure that everything was up to date.

[Next page](https://forums.rockylinux.org/t/epel-broken-now-what/13887.md?page=2)
