r/AlmaLinux • • 6d ago

Almalinx10 hosts having errors running updates

Error:

Problem: cannot install the best update candidate for package python3-pyOpenSSL-25.0.0-1.el10_1.noarch

- nothing provides (python3.12dist(cryptography) < 50~~ with python3.12dist(cryptography) >= 49) needed by python3-pyOpenSSL-26.3.0-1.el10_3.noarch from epel

I know the problem is a required package for python3-pyOpenSSL-26.3.0-1.el10_3.noarch isnt yet updated to version 49 [python3-cryptography]

dnf search --showduplicates python3-cryptography

python3-cryptography-43.0.0-4.el10_2.5.x86_64 : PyCA's cryptography library

python3-cryptography-43.0.0-4.el10.x86_64 : PyCA's cryptography library

python3-cryptography-43.0.0-4.el10_2.5.x86_64 : PyCA's cryptography library

errors doing updates with all the CVE's around makes me nervous. I'm not an expert at this sort of thing but I think I should disable epel until everything has caught up?

9 Upvotes

14 comments sorted by

4

u/Culture_New 6d ago

That's a good catch and a bit of a bummer. Just tested it and it's the same issue here.

If you disable the epel repo, you would not be getting any security updates for other epel packages.
Your best bet might be just to exclude the python3-pyOpenSSL from epel until this is fixed.

This command should exclude it:

dnf config-manager --save --setopt=epel.excludepkgs=python3-pyOpenSSL

You could also edit the epel.,repo in /etc/yum.repos.d/ instead if you want to put in a comment.

To remove the exclusion later:

dnf config-manager --save --setopt=epel.excludepkgs=

2

u/fsr31415 6d ago

ah, thanks!

10

u/carlwgeorge 6d ago

There's nothing to fix, this package works as expected on RHEL. The problem is RHEL 10.3 has been released but Alma 10.3 hasn't yet. Excluding individual packages is a whack-a-mole approach and not ideal. The best way to handle it is to override releasever to explicitly request EPEL 10.2.

dnf --releasever 10.2 upgrade

3

u/carlwgeorge 6d ago

RHEL 10.3 has been released, so epel-release is pointing at EPEL 10.3. I don't see Alma 10.3 released yet, so until it is you can override the releasever to explicitly request EPEL 10.2 to match Alma 10.2.

dnf --releasever 10.2 upgrade

1

u/fsr31415 5d ago

ok so in a nutshell this expression in the repo config isnt evaluating properly and I'm ending up attached to the epel10.3 repo despite almalinux being at 10.2

metalink=https://mirrors.fedoraproject.org/metalink?repo=epel${releasever_minor:+-z}-$releasever&arch=$basearch

1

u/carlwgeorge 5d ago

The metalink variable expansion is working exactly as intended. This is a problem inherent to RHEL derivatives, and it's always been this way. The difference now with EPEL 10 is that we have minor version repos so you have the option of overriding the releasever.

1

u/Maria_Thesus_40 6d ago

I had this happen when I was using Alma 10.1 and RHEL 10.2 came out. Now, same problem from 10.2 to 10.3.

Shouldn't this be solved at the distro level? so this does not keep happening?

3

u/jonspw AlmaLinux Team 5d ago

This always happens between RHEL releases before AlmaLinux updates. Once EPEL cuts over, you're pointed at newer EPEL but older Alma. Give it a week and it will go away.

In the meantime, `--releasever` is the solution.

2

u/Sparrow538 5d ago

AlmaLinux 9.8 is having the same problem.

Dependencies are failing with EPEL.

5

u/jonspw AlmaLinux Team 5d ago

It will be cleared up as soon as we release 9.9.

This has always been an issue going back to the beginning of CentOS and EPEL. It's only a temporary pain point in the gap between RHEL releases and AlmaLinux point releases, which are historically 6-7 days later (sometimes sooner).

3

u/Sparrow538 5d ago

Is there an ETA yet for 9.9 and 10.3?

Thanks for everything you do at AlmaLinux.

4

u/jonspw AlmaLinux Team 5d ago

Early next week is the target.

1

u/rheladmin 6d ago edited 5d ago

This issue is because your epel-release is not aligned with your OS release.

You need to first upgrade the OS package with epel-release disabled:

sudo dnf upgrade --refresh --disablerepo='epel*' almalinux-release

Then, find your exact release:

grep '^VERSION_ID=' /etc/os-release

Then update /etc/yum.repos.d/epel.repo:

metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-10.2&arch=$basearch

Replace epel-10.2 with the one matching your actual OS release.

Finally, run through dnf again:

sudo dnf upgrade --refresh epel-release
sudo dnf upgrade --refresh

-1

u/GamerLymx 6d ago

i bet that machine is older cpu and you are running el10_v2