Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only install fuse-sshfs from epel #3096

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

afbjorklund
Copy link
Member

@afbjorklund afbjorklund commented Jan 8, 2025

The other packages are available in the system distribution.

The extra packages (from EPEL) should not be used for them.

Note: Fedora EPEL means "Extra Packages for Enterprise Linux"

For CentOS Stream, the repository is actually called "EPEL-Next"

The regular "EPEL" repository was used for CentOS Linux only.

But we won't bother with that, until it is actually needed by Lima...

In RHEL 8 sshfs was available in PowerTools, so support that as well.

Closes #2979


https://docs.fedoraproject.org/en-US/epel/

EPEL-Next is not a complete rebuild of all the EPEL packages, but only those packages that need to be rebuilt to install on CentOS Stream. The EPEL-Next repo is meant to be layered on top of the regular EPEL repository.

@afbjorklund
Copy link
Member Author

afbjorklund commented Jan 8, 2025

The installation of epel-release-next was actually excluded by install_weak_deps=False

Requires:       redhat-release >=  %{version}
# epel-release is only for enterprise linux, not fedora
Conflicts:      fedora-release
# crb needs config-manager to run
# But only recommend it, incase people do not need crb
Recommends:     dnf-command(config-manager)
%if %{with next}
Recommends:     (epel-next-release if centos-stream-release)
%endif

So if you do a dnf upgrade --enablerepo=epel, then it will be included in the updates:

Installing weak dependencies:
 epel-next-release       noarch     9-9.el9                 epel          7.9 k

Then you can choose to disable it, or enable both of them (as epel-next requires epel)

yum-config-manager --disable epel-next

yum-config-manager --enable epel

But this only happens on CentOS Stream (i.e. Next), not on Enterprise Linux (e.g. AlmaLinux)

Since it is stable, it only has epel-release (released packages) but not epel-next-release.

https://docs.fedoraproject.org/en-US/epel/epel-about-next/

@afbjorklund

This comment was marked as off-topic.

@AkihiroSuda
Copy link
Member

Needs rebase

The other packages are available in the system distribution.

The extra packages (from EPEL) should not be used for them.

Signed-off-by: Anders F Björklund <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

centos-stream-9: sudo dnf upgrade fails (due to iptables-legacy and iptables-libs conflicts)
2 participants