Augeas-devel not found on my system

Rocky Linux Help & Support
1

I every all

Today, I have a problem to install augeas-devel on my system, buy yum say “rror: Unable to find a match: augeas-devel” but I see that it’s availlable here : Rocky Linux Repository

Why I can’t install it ?

Need epel-release or another repository ?

Thanks

2

Just do:

dnf --enablerepo=devel install augeas-devel

since devel repo is not enabled by default. A repo needs to be enabled or you need to pass a command like above to temporarily enable to install packages, etc.

3 
sudo dnf install epel-release
sudo dnf config-manager --set-enabled crb

Then try again

Just saw Iwalker reply. So it appears to be available in both rocky-devel repo and on epel as per this:

$ sudo dnf install augeas-devel
Last metadata expiration check: 0:11:20 ago on Sat 11 Apr 2026 07:04:31 AM EDT.
Dependencies resolved.
================================================================================
 Package               Arch        Version                 Repository      Size
================================================================================
Installing:
 augeas-devel          x86_64      1.14.1-3.el9            crb             18 k
Installing dependencies:
 cmake-filesystem      x86_64      3.26.5-3.el9_7          appstream

So you have to pick one or the other.

4

Hmm strange that crb and devel have exactly the same version. Surprised it appears in two places but I guess there is a reason for it.

Incidently, crb is a Rocky repo, so epel isn’t needed for it. So it’s also just enough to enable the crb repo and use that, or the devel one. The only time you would need epel for it is if you wanted to use crb enable instead of the dnf config-manager --set-enabled crb command.

5

Thank you for your help ! It’s work ! Bye

6

I guess I don’t understand the relationship between the two repos that causes crb to be enabled in the different ways stated above. This is more for future reference so I don’t give erroneous help.

7

To use crb enable, this command is provided by the epel-release package. If for example you haven’t installed epel-release then you won’t be able to use it. In which case you can use the longer dnf command as you mentioned, so dnf config-manager --set-enabled crb.

Both effectively do the same job, just crb enable can only be used as the epel-release package provides the /usr/bin/crb binary.

8

So it’s a convenience provided by epel for whatever reason. Why does epel provide a binary “crb” for the repository crb? There’s no man page for crb so I’d have to download the crb source to know what it does. I guess this goes back into the history of the creation of the epel repo back when “Powertools” was the redhat extra tools repo.

9

Apparently powertools was named because of a grey area by calling it codeready-builder (was supposedly copyrighted or something like that), but since like RHEL9 and higher it’s been fine to use crb as the shortcut for codeready-builder. EPEL probably provides the command for convenience, since crb enable is far shorter than writing dnf config-manager --set-enabled crb and that’s about all it does is save you a bit of time. Also, because some EPEL packages rely on packages from crb repository as dependencies.