On Mon, 2022-06-13 at 07:41 -0400, Josh Boyer wrote:
On Sun, Jun 12, 2022 at 6:50 AM Sérgio Basto
<sergio(a)serjux.com>
wrote:
>
> On Sun, 2022-06-05 at 00:54 +0200, Neal Gompa wrote:
> > Let me start with examples that I get *regularly*: Pagure fails
> > to
> > install from EPEL on RHEL/CentOS/Alma/etc. because python3-
> > markdown
> > is
> > not available. KDE Plasma fails to install because of a mass of
> > missing dependencies.
>
> if epel use crb to build some package, crb should be enabled when
> we
> install epel repo, yes , that is my opinion
If the dependency is only needed at build time, which is what CRB
content is intended for, then there is no reason to default to having
CRB enabled because nothing will be installed from CRB anyway. The
issue that people are running into is that EPEL packages have
developed *runtime* dependencies on CRB content. For a subset of
users, that is probably fine. However, if a package needs something
at runtime it would be better to first inquire about putting that
dependency in BaseOS or AppStream rather than just blindly using it
from CRB.
at least [1] we should be add to BaseOS or AppStream
[1]
aspell.x86_64 12:0.60.8-8.el9 @crb
poppler-qt5.x86_64 21.01.0-12.el9 @crb
python3-markdown
I got the results running `dnf --disablerepo=crb list extras`
josh
_______________________________________________
epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org
To unsubscribe send an email to
epel-devel-leave(a)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.fedoraproj...
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
--
Sérgio M. B.